Heap corruption via Aura use-after-free
Published Jul 20, 2026 · Updated Jul 20, 2026
Use-after-free in Aura in Google Chrome before 150.0.7871.128 allows local users to corrupt heap memory through a malicious file. Public records identify Aura as the affected component but do not disclose the freed object's lifetime error, file format, or triggering code path because the Chromium issue remains restricted. Exploitation requires user interaction with a local file; successful heap corruption affects data confidentiality, integrity, and browser availability.
Summary
What happened
Use-after-free in Aura in Google Chrome before 150.0.7871.128 allows local users to corrupt heap memory through a malicious file. Public records identify Aura as the affected component but do not disclose the freed object's lifetime error, file format, or triggering code path because the Chromium issue remains restricted. Exploitation requires user interaction with a local file; successful heap corruption affects data confidentiality, integrity, and browser availability.
The record
- CVE
- CVE-2026-15905
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=150.0.7871.128 <150.0.7871.128
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.
Weakness, pattern, technique
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