Sandboxed code execution via WebRTC heap overflow
Published May 20, 2026 · Updated May 20, 2026
Heap buffer overflow in WebRTC in Google Chrome before 148.0.7778.179 allows remote attackers to execute sandboxed code via crafted HTML. Google identifies the affected component and overflow class but has not published the faulty WebRTC operation because the issue remains restricted. A user must open the attacker-controlled page; successful exploitation executes arbitrary code inside the browser sandbox, with no documented sandbox escape.
Summary
What happened
Heap buffer overflow in WebRTC in Google Chrome before 148.0.7778.179 allows remote attackers to execute sandboxed code via crafted HTML. Google identifies the affected component and overflow class but has not published the faulty WebRTC operation because the issue remains restricted. A user must open the attacker-controlled page; successful exploitation executes arbitrary code inside the browser sandbox, with no documented sandbox escape.
The record
- CVE
- CVE-2026-9119
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 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.179 <148.0.7778.179
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.
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