Process-memory disclosure via WebAudio heap overflow
Published Apr 8, 2026 · Updated Apr 8, 2026
Heap buffer overflow in Google Chrome WebAudio before 147.0.7727.55 allows remote attackers to read process memory via crafted HTML. Google identifies the WebAudio component and heap-overrun class, but the restricted issue does not disclose the responsible function, buffer allocation, or write operation. Exploitation requires a user to load the attacker-controlled page; the published impact is limited to disclosure of potentially sensitive process-memory contents.
Summary
What happened
Heap buffer overflow in Google Chrome WebAudio before 147.0.7727.55 allows remote attackers to read process memory via crafted HTML. Google identifies the WebAudio component and heap-overrun class, but the restricted issue does not disclose the responsible function, buffer allocation, or write operation. Exploitation requires a user to load the attacker-controlled page; the published impact is limited to disclosure of potentially sensitive process-memory contents.
The record
- CVE
- CVE-2026-5864
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.55 <147.0.7727.55
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