Code execution via unsigned automatic updates
Published May 11, 2026 · Updated May 11, 2026
Improper signature verification in Zen Browser before 1.19.9b allows attackers to execute code through unsigned automatic updates. The org.mozilla.updater binary was built with --enable-unverified-updates, so it accepts MAR packages without cryptographic signatures or a bound channel identifier. Exploitation requires compromise of the update server or release pipeline; a matching SHA-512 hash is checked, but attacker-supplied code then runs on affected clients.
Summary
What happened
Improper signature verification in Zen Browser before 1.19.9b allows attackers to execute code through unsigned automatic updates. The org.mozilla.updater binary was built with --enable-unverified-updates, so it accepts MAR packages without cryptographic signatures or a bound channel identifier. Exploitation requires compromise of the update server or release pipeline; a matching SHA-512 hash is checked, but attacker-supplied code then runs on affected clients.
The record
- CVE
- CVE-2026-41431
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Zen Browser
- Product
- Zen Browser
- Classifications
- CWE-347, T1195.002
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.19.9b
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Structural proof of missing MAR verificationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo