Sandbox escape via incorrect Graphics boundary conditions
Published Sep 15, 2026 · Updated Sep 15, 2026
Sandbox escape in the Graphics component in Firefox before 156 and Firefox ESR before 153.3 allows attackers to cross the process sandbox. Mozilla identifies incorrect boundary conditions as the cause but has not disclosed the affected code path, malformed input, or faulty boundary operation. The public record does not state required privileges, user interaction, delivery vector, or post-escape capability, so the bounded consequence is escape from the browser process sandbox.
Summary
What happened
Sandbox escape in the Graphics component in Firefox before 156 and Firefox ESR before 153.3 allows attackers to cross the process sandbox. Mozilla identifies incorrect boundary conditions as the cause but has not disclosed the affected code path, malformed input, or faulty boundary operation. The public record does not state required privileges, user interaction, delivery vector, or post-escape capability, so the bounded consequence is escape from the browser process sandbox.
The record
- CVE
- CVE-2026-92035
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
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
No public exploit references are available in this record.
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