Sandbox escape via Mojo integer overflow
Published Jun 25, 2026 · Updated Jun 25, 2026
Integer overflow in Google Chrome's Mojo before 149.0.7827.201 allows remote attackers with a compromised renderer to escape the sandbox. Google has not disclosed the affected Mojo code path or the arithmetic operation that overflows while processing the malicious file. Exploitation requires prior renderer compromise and user interaction with that file, after which code can cross the renderer sandbox boundary.
Summary
What happened
Integer overflow in Google Chrome's Mojo before 149.0.7827.201 allows remote attackers with a compromised renderer to escape the sandbox. Google has not disclosed the affected Mojo code path or the arithmetic operation that overflows while processing the malicious file. Exploitation requires prior renderer compromise and user interaction with that file, after which code can cross the renderer sandbox boundary.
The record
- CVE
- CVE-2026-13281
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-472, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=149.0.7827.201 <149.0.7827.201
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
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