Mozilla Revokes GPG Signing Key After Accidental Upload to Private GitHub Repository
Mozilla has revoked and replaced a GPG signing key after an unencrypted copy of the secret key was accidentally uploaded to a private GitHub repository. The key had been used to sign Linux archives, RPM packages, and associated checksum files for Firefox and Thunderbird.
The incident created a theoretical risk that an attacker could have used the key to sign malicious installers and present them as official releases. However, Mozilla assessed the supply-chain risk as low because the repository was accessible only to a limited group of internal employees who already possessed legitimate access to the key.
Audit log reviews showed no indications that the key had been accessed or misused by unauthorized parties. As a result, the company revoked the old key and issued a replacement that will remain valid until 5 August 2028.
Most end users do not need to take any action. Individuals who manually verify GPG signatures on downloaded files must import the new public key and the revocation certificate for the previous key.
Users installing Firefox from RPM packages on Linux distributions may face additional steps. Depending on the distribution, they will need to update the signing key manually; otherwise, newer browser versions may fail to install. Mozilla has published specific instructions for Fedora, RHEL, Rocky Linux, AlmaLinux, openSUSE, and SUSE.
Thunderbird users are not affected by the RPM-related instructions because the mail client does not provide official RPM packages. Updated public key material and revocation information are available in the current KEY files for Firefox Nightly and on the keys.openpgp.org server.
Mozilla stated it will implement additional safeguards to prevent secret keys from being committed to repositories in the future.
Related articles
Protestware: How Ideologically Motivated Attackers Compromise Open Source Code and Supply Chains
Protestware represents a growing supply chain risk where open source maintainers deliberately insert destructive or politically motivated code into widely used packages. Unlike traditional malware seeking financial gain, protestware is driven by ideological motives and can delete files, cause denial of service, or restrict functionality based on geography or locale. Notable incidents include the node-ipc and peacenotwar packages that overwrote files on systems in Russia and Belarus, the colors.js infinite loop causing DoS, and es5-ext triggering high CPU usage during specific hours or Russian locales. These attacks often hide in postinstall hooks, use geolocation checks via ipinfo.io, or activate via environment variables and timestamps. Detection requires static analysis for geo-IP logic, dynamic monitoring in sandboxes, and tools such as Software Bill of Materials and OpenSSF Scorecard. Organizations are advised to adopt Zero Trust for dependencies, pin versions, use internal artifact repositories, and follow frameworks including NIST SSDF and SLSA to mitigate risks.
Attackers Exploit Critical JFrog Artifactory Flaw CVE-2026-82329 to Forge Admin Tokens and Poison CI/CD Pipelines
A critical vulnerability tracked as CVE-2026-82329 in JFrog Artifactory is being actively exploited in the wild, allowing unauthenticated attackers with network access to generate or forge administrator tokens on self-managed installations that retain default settings. The flaw enables full authentication bypass, granting attackers administrative privileges to enumerate users and groups, access sensitive configurations, read stored artifacts, and modify security settings. The greatest risk arises when Artifactory serves as the central repository for automated CI/CD pipelines, where an attacker can replace trusted internal packages, container images, or dependencies and propagate malicious changes downstream into build runners and production environments. JFrog has released patches for multiple branches, including versions 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, and 7.161.20, although patching alone does not invalidate already-issued tokens. Organizations are advised to restrict network exposure, revoke and rotate admin tokens, review audit logs for anomalous token generation and configuration changes, and validate artifact integrity across the vulnerable period. The issue does not affect JFrog Cloud instances.
Critical JFrog Artifactory Flaw CVE-2026-82329 Actively Exploited to Forge Admin Tokens in Self-Managed Deployments
A critical vulnerability identified as CVE-2026-82329 in JFrog Artifactory is being actively exploited in the wild, enabling unauthenticated attackers to generate or forge administrator tokens simply by having network access to affected instances. The flaw impacts self-managed installations that retain default configurations, a common scenario when repositories are deployed quickly and later exposed to the internet. Once administrative access is obtained, attackers can enumerate users and groups, access sensitive configurations, read stored artifacts, and modify security settings. The most severe risk arises when Artifactory automatically feeds CI/CD pipelines, allowing malicious substitution of trusted packages, container images, or dependencies that then propagate downstream into production environments. JFrog Cloud instances were already protected, while self-managed deployments require updates to specific patched versions including 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, or 7.161.20. Even after patching, previously issued tokens must be revoked because their validity operates independently of the software update. Organizations are advised to restrict network exposure, rotate credentials, audit token generation logs, and validate artifact integrity for any material published during the vulnerable period.
Unicode Tricks Let Malicious Python Code Bypass Code Review
A detailed analysis shows how subtle Unicode manipulations allow code to pass human review while executing entirely different logic. The first technique replaces Latin characters with visually identical Cyrillic or other script letters inside identifiers, such as using Ukrainian 'і' instead of Latin 'i' in an is_admin variable. Python treats these as distinct names because NFKC normalization does not map Cyrillic to Latin. The second technique inserts bidirectional override characters that reorder text for the compiler while the editor displays the intended order. The third hides zero-width characters inside string literals to break comparisons and searches. A compact Python auditor using the tokenize module and explicit character sets detects all three classes of characters. The article recommends adding such checks to CI pipelines and configuring linters including ruff and flake8 to reject suspicious commits.