Mozilla has withdrawn the cryptographic key used to sign Firefox and Thunderbird downloads for Linux after an unencrypted version was accidentally committed to one of the company's private code repositories. The key allows users and Linux distributions to verify that a downloaded Firefox tarball originated from Mozilla and wasn't altered in transit. While the repository remained private and Mozilla found no evidence of unauthorized access, the company revoked the key regardless, marking the first time in over a decade that it has pulled a signing key for reasons other than scheduled expiry.
The revoked subkey, which carried the fingerprint 09BE ED63 F346 2A2D FFAB 3B87 5ECB 6497 C1A2 0256 and was announced in April 2025, had been scheduled to remain valid until March 2027—making the swap roughly seven months ahead of schedule. Mozilla typically rotates this subkey approximately every two years as a safeguard against leaks the company might never detect. The replacement subkey, published Monday, bears the fingerprint 827E 6586 0867 9618 CD34 9F93 678E 455D 7676 7AA3 and remains valid through August 5, 2028. An examination of Mozilla's public key repository revealed five earlier signing subkeys dating back to 2015, all of which were retired through expiry rather than revocation.
The revocation certificate published alongside the new key carries reason code 2—"key material has been compromised"—generated on August 6, 2026 at 11:14 UTC with the notation "We no longer trust this key." According to the OpenPGP standard RFC 4880, a key marked as superseded or retired leaves its prior signatures intact, while a key revoked due to compromise renders every signature it ever created suspect. Mozilla's own incident account stops short of stating the key was stolen, noting instead that a review of available audit records showed no sign of unauthorized access and that everyone with visibility to the repository already possessed legitimate access. The company has not disclosed which repository contained the key, how long it remained there, or the specific safeguards it has implemented in response.
The change creates immediate consequences for two user groups, while most Firefox and Thunderbird users need take no action. Anyone who manually verifies signatures must import both the new key and the revocation certificate for the old one, as files signed with the previous key will fail verification once a user imports the revocation—affecting older Firefox and Thunderbird downloads, not just future releases. Users installing Firefox from Mozilla's RPM packages may encounter failed updates and need to manually replace the key, as some distributions see dnf fetch the updated key automatically and prompt for fingerprint confirmation, while others fail outright with messages indicating installed repository keys are incorrect. The old key must be removed first because rpm --import can report success while leaving the stale key in place. Thunderbird faces no RPM complications because it publishes no official RPM packages, and Mozilla has said nothing about the APT repository serving Debian and Ubuntu users, which relies on a separate key. For organizations and developers who depend on verified software supply chains, the episode illustrates how even inadvertent exposure within controlled environments can force sweeping operational responses that cascade through distribution channels and user workflows.