Out-of-bounds memory access via use-after-free
Published Nov 6, 2025 · Updated Nov 6, 2025
Use-after-free in Google Chrome Safe Browsing before 141.0.7390.107 allows remote attackers to access out-of-bounds memory via crafted HTML. Google identifies Safe Browsing as the affected component but has not disclosed the freed object's lifetime error or the code path that reuses it. Exploitation requires a renderer compromise and can extend memory access beyond the renderer's intended bounds; no independent code-execution outcome is published.
Summary
What happened
Use-after-free in Google Chrome Safe Browsing before 141.0.7390.107 allows remote attackers to access out-of-bounds memory via crafted HTML. Google identifies Safe Browsing as the affected component but has not disclosed the freed object's lifetime error or the code path that reuses it. Exploitation requires a renderer compromise and can extend memory access beyond the renderer's intended bounds; no independent code-execution outcome is published.
The record
- CVE
- CVE-2025-11756
- Published
- Nov 6, 2025
- Updated
- Nov 6, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2025CVE publishedPublication date reported by the CVE source.
- Nov 6, 2025Record 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=141.0.7390.107 <141.0.7390.107
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