Skip to content
Tech News
← Back to articles

Mozilla updates GPG signing key for Firefox releases after exposure

read original more articles
Why This Matters

Mozilla's update of the GPG signing key for Firefox and Thunderbird highlights the importance of maintaining secure software supply chains. While the risk of malicious actors exploiting the exposed key remains low, the incident underscores the need for rigorous key management and prompt response to potential security breaches in the tech industry.

Key Takeaways

Mozilla announced today that it updated the GPG key used to sign Firefox and Thunderbird releases after it was accidentally exposed on GitHub.

However, in a Monday blog post, it noted that the risk of a supply chain attack in which threat actors could distribute malicious installers signed with the exposed key is low because only a limited number of individuals had access to the GitHub repository.

Additionally, Mozilla has yet to find evidence that the previous GPG key was accessed by unauthorized parties while being exposed.

After discovering the incident, the organization revoked the key used to sign Linux tarballs, RPM packages, and checksum files, and has taken measures to prevent similar issues in the future.

"Today, we moved to a new GPG signing subkey used to sign certain Firefox and Thunderbird artifacts (namely Linux tarballs, RPM packages, checksums files) after an unencrypted copy of the previous subkey was inadvertently committed to a private GitHub repository," it noted.

"Our review of available audit records found no evidence that the key was accessed by an unauthorized party while it was present in the repository. Access to the repository was limited to a small group within Mozilla, all of whom already had authorized access to the key through other means."

While most users will not have to take any action after the GPG key's rotation, Mozilla says that users who manually verify GPG signatures must import the new signing key and the revocation for the old key.

It also added that Linux users who install Firefox using RPM packages may need to manually update their systems and shared detailed instructions on what actions are required on systems running Fedora 43 and later, Fedora 42 and older, RHEL/Rocky/Almalinux, and openSUSE/SUSE-based distributions to continue receiving the latest Firefox updates.

Since Thunderbird does not provide official RPM packages, no RPM-specific action is required for Thunderbird users.

The new signing subkey expires August 5, 2028, and the new public key and revocation for the previous key are available through the latest Firefox Nightly KEY files and keys.openpgp.org.