Process-memory disclosure via undisclosed ANGLE validation flaw
Published Jun 30, 2026 · Updated Jun 30, 2026
Insufficient input validation in ANGLE in Google Chrome before 150.0.7871.47 allows remote attackers to read process memory via crafted HTML. Google has not disclosed the ANGLE code locus, the untrusted field, or the validation operation that permits the read. Exploitation requires a compromised renderer and user interaction with a crafted page; the reported consequence is memory disclosure only.
Summary
What happened
Insufficient input validation in ANGLE in Google Chrome before 150.0.7871.47 allows remote attackers to read process memory via crafted HTML. Google has not disclosed the ANGLE code locus, the untrusted field, or the validation operation that permits the read. Exploitation requires a compromised renderer and user interaction with a crafted page; the reported consequence is memory disclosure only.
The record
- CVE
- CVE-2026-13877
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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.47 <150.0.7871.47
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