Sandboxed code execution via WebAudio implementation
Published Jul 21, 2026 · Updated Jul 21, 2026
Inappropriate implementation in WebAudio in Google Chrome before 150.0.7871.182 allows remote attackers to execute sandboxed code. The public advisory identifies WebAudio as the locus but does not disclose which input or operation is implemented incorrectly; Chromium keeps the underlying issue restricted. A user must open a crafted HTML page, and the reported result is code execution inside Chrome's sandbox rather than a sandbox escape.
Summary
What happened
Inappropriate implementation in WebAudio in Google Chrome before 150.0.7871.182 allows remote attackers to execute sandboxed code. The public advisory identifies WebAudio as the locus but does not disclose which input or operation is implemented incorrectly; Chromium keeps the underlying issue restricted. A user must open a crafted HTML page, and the reported result is code execution inside Chrome's sandbox rather than a sandbox escape.
The record
- CVE
- CVE-2026-16421
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 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.182 <150.0.7871.182
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