Security News

Mozilla Replaces Firefox Signing Key After Accidental Public Exposure

Security Week · 11 Aug 2026
Key Takeaway Regularly audit your code repositories and cloud storage for accidentally exposed passwords, keys, or certificates, and rotate them immediately if found.

Mozilla has issued a new GPG signing key for Firefox after discovering that a previous signing subkey had been inadvertently added to a public GitHub repository. GPG keys are used to verify that software releases are genuine and haven't been tampered with, so exposing one raises concerns that it could be misused to sign malicious files that appear to come from a trusted source.

In response, Mozilla revoked the exposed subkey and issued a replacement, a standard precaution when cryptographic material may have been compromised. There is no indication in the report that the exposed key was actually exploited by attackers, but revoking it removes the risk entirely.

This incident is a reminder that even major software vendors can accidentally expose sensitive credentials, often through simple mistakes like committing files to public code repositories. For small businesses that rely on open-source tools or manage their own code repositories, it highlights the importance of scanning for accidentally exposed secrets and rotating credentials quickly when exposure occurs.

Mozilla Firefox data exposure credential security software supply chain
Carrying this risk through a supplier? Assessing third-party and supply chain security ->

Summarised by CISO AI from Security Week. We link back to every original so you can read it yourself.