Sandbox escape via Tint type confusion
Published Jul 1, 2026 · Updated Jul 1, 2026
Type confusion in Tint in Google Chrome before 150.0.7871.46 allows remote attackers to escape the browser sandbox via crafted HTML. Google has not published the faulty Tint code path or the incompatible type operation that processes the page content. Exploitation requires a user to open attacker-controlled HTML, after which the attacker gains execution beyond Chrome's sandbox boundary.
Summary
What happened
Type confusion in Tint in Google Chrome before 150.0.7871.46 allows remote attackers to escape the browser sandbox via crafted HTML. Google has not published the faulty Tint code path or the incompatible type operation that processes the page content. Exploitation requires a user to open attacker-controlled HTML, after which the attacker gains execution beyond Chrome's sandbox boundary.
The record
- CVE
- CVE-2026-14423
- Published
- Jul 1, 2026
- Updated
- Jul 1, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2026CVE publishedPublication date reported by the CVE source.
- Jul 1, 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=150.0.7871.46 <150.0.7871.46
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