Heap corruption via unlocked Web Audio buffers
Published Mar 9, 2021 · Updated Oct 21, 2025
A data race in Google Chrome before 89.0.4389.72 allows remote attackers to corrupt heap memory through a crafted HTML page. ScriptProcessorNode::process() exposes shared input and output audio buffers to the main and audio-rendering threads without holding its mutex across processing. Activating the page's Web Audio code is required; concurrent sorting causes an out-of-bounds write, and observed exploitation likely chained a sandbox escape.
Summary
What happened
A data race in Google Chrome before 89.0.4389.72 allows remote attackers to corrupt heap memory through a crafted HTML page. ScriptProcessorNode::process() exposes shared input and output audio buffers to the main and audio-rendering threads without holding its mutex across processing. Activating the page's Web Audio code is required; concurrent sorting causes an out-of-bounds write, and observed exploitation likely chained a sandbox escape.
The record
- CVE
- CVE-2021-21166
- Published
- Mar 9, 2021
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-362, CAPEC-26, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 2021Exploitation reportedCISA Known Exploited Vulnerabilities listing
- Oct 21, 2025Record 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=unspecified <89.0.4389.72
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
- ScriptProcessorNode race proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Google-reported exploitation in the wildreported exploitation
- CISA Known Exploited Vulnerabilities listingknown exploited catalog
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