Memory disclosure via Frame out-of-bounds read
Published Jul 30, 2026 · Updated Jul 30, 2026
Out-of-bounds read in Frame in Google Chrome before 151.0.7922.72 allows remote attackers to access process memory via a crafted HTML page. Google identifies the Frame component but has not disclosed which operation mishandles attacker-controlled page data or which boundary check is missing. A user must load the crafted page; public material establishes memory exposure but reports neither code execution nor sandbox escape.
Summary
What happened
Out-of-bounds read in Frame in Google Chrome before 151.0.7922.72 allows remote attackers to access process memory via a crafted HTML page. Google identifies the Frame component but has not disclosed which operation mishandles attacker-controlled page data or which boundary check is missing. A user must load the crafted page; public material establishes memory exposure but reports neither code execution nor sandbox escape.
The record
- CVE
- CVE-2026-17971
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=151.0.7922.72 <151.0.7922.72
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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