Summary
- Mozilla exposed a private GPG signing subkey but found no evidence that an unauthorized party accessed or misused it.
- Most users need to do nothing, but manual GPG verifiers and some Firefox RPM users must replace the revoked key.
- The incident shows that Linux’s security still depends on software publishers and repositories protecting their parts of the trust chain.
Mozilla has admitted that it exposed a private GPG signing subkey in a private GitHub repository, forcing the company to revoke and replace it. The key was used for certain Firefox and Thunderbird release files distributed to Linux users.
Affected users should check Mozilla’s official instructions for replacing the signing key. The announcement contains separate directions for the affected distributions, along with the steps needed to verify the replacement key.
What is a signing key?
It's pretty important for privacy
Linux users often praise their operating system of choice over Windows and macOS for its security advantages. One such advantage is the availability of different methods for downloading Linux software safely, including checking signatures and sticking to trusted sources. However, Mozilla’s mistake demonstrates that even those protections have a weak point: the publisher must keep its private signing key private.
A signing key functions somewhat like a digital seal placed on a software release. Mozilla uses its private key to sign a file, so that users and package managers can use the corresponding public key to verify the signature. A successful verification confirms that the file genuinely came from Mozilla and that nobody modified it after Mozilla signed it.
Thankfully, Mozilla says access to the private GitHub repository was restricted to a small number of people within the company, all of whom were already authorized to access the key. Its review of the available audit records found no evidence that an unauthorized party accessed the key while it was present in the repository.
Nevertheless, an exposed private signing key could present a serious risk. In theory, a malicious package could be signed and be presented as though it came directly from Mozilla. An attacker would still need to find a way to distribute that package to potential victims, but its apparently legitimate signature could make it considerably harder to detect.
Who's on cleanup duty now?
The affected artifacts were Linux tarballs, Firefox RPM packages, and checksum files for Firefox and Thunderbird. Most people using either application do not need to take any action. However, Mozilla has identified two groups that may need to update the key they currently trust.
The first group consists of Linux users who manually verify Mozilla’s GPG signatures for Firefox or Thunderbird downloads. These users must import Mozilla’s new signing key after the revocation of the previous one. The second group consists of people who obtain Firefox through Mozilla’s RPM packages.
This incident was caused by Mozilla rather than a vulnerability within Linux itself. Still, it challenges the idea that choosing Linux automatically makes a computer bulletproof. That point was demonstrated even more forcefully in June 2026, when over 1,500 packages in the Arch User Repository were reportedly compromised.