Sandbox-external memory disclosure via CrashReporting over-read
Published Sep 3, 2026 · Updated Sep 3, 2026
Out-of-bounds read in Google Chrome before 152.0.7977.82 allows remote attackers to read memory outside the sandbox via crafted HTML. The CrashReporting component reads beyond an intended memory boundary, but Google has not disclosed the affected function or malformed field that causes the read. Exploitation requires a renderer process already compromised and user interaction with the page, limiting the reported consequence to memory disclosure.
Summary
What happened
Out-of-bounds read in Google Chrome before 152.0.7977.82 allows remote attackers to read memory outside the sandbox via crafted HTML. The CrashReporting component reads beyond an intended memory boundary, but Google has not disclosed the affected function or malformed field that causes the read. Exploitation requires a renderer process already compromised and user interaction with the page, limiting the reported consequence to memory disclosure.
The record
- CVE
- CVE-2026-85052
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 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=152.0.7977.82 <152.0.7977.82
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