Sandboxed code execution via Runtime type confusion
Published May 6, 2026 · Updated May 6, 2026
Type confusion in Google Chrome Runtime before 148.0.7778.96 allows remote attackers to execute arbitrary code in a sandbox via crafted HTML. The public record identifies Runtime as the affected component but does not disclose the incompatible types, code locus, or erroneous operation because the Chromium issue remains restricted. Successful exploitation requires a user to open attacker-controlled HTML; resulting code execution remains confined to Chrome's sandbox, with no documented sandbox escape.
Summary
What happened
Type confusion in Google Chrome Runtime before 148.0.7778.96 allows remote attackers to execute arbitrary code in a sandbox via crafted HTML. The public record identifies Runtime as the affected component but does not disclose the incompatible types, code locus, or erroneous operation because the Chromium issue remains restricted. Successful exploitation requires a user to open attacker-controlled HTML; resulting code execution remains confined to Chrome's sandbox, with no documented sandbox escape.
The record
- CVE
- CVE-2026-7927
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=148.0.7778.96 <148.0.7778.96
What conditions does exploitation require?
What is affected?
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