Sandboxed code execution via WebRTC use-after-free
Published Apr 28, 2026 · Updated Apr 28, 2026
Use after free in WebRTC in Google Chrome before 147.0.7727.138 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies the locus only as WebRTC; restricted bug details do not disclose which object is freed or which stale reference later accesses it. A user must load attacker-controlled HTML, and the resulting code remains confined to Chrome's sandbox absent a separate escape.
Summary
What happened
Use after free in WebRTC in Google Chrome before 147.0.7727.138 allows remote attackers to execute code in the sandbox via crafted HTML. Google identifies the locus only as WebRTC; restricted bug details do not disclose which object is freed or which stale reference later accesses it. A user must load attacker-controlled HTML, and the resulting code remains confined to Chrome's sandbox absent a separate escape.
The record
- CVE
- CVE-2026-7341
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=147.0.7727.138 <147.0.7727.138
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