Process-memory disclosure via extension policy bypass
Published Nov 10, 2025 · Updated Nov 10, 2025
Policy bypass in Google Chrome before 142.0.7444.59 allows attackers to read potentially sensitive process memory via a crafted extension. Public records identify the Extensions component but do not disclose which policy check is bypassed or which operation exposes process memory. Exploitation requires convincing a user to install a malicious Chrome extension; the documented consequence is memory disclosure, with no reported write or service-interruption capability.
Summary
What happened
Policy bypass in Google Chrome before 142.0.7444.59 allows attackers to read potentially sensitive process memory via a crafted extension. Public records identify the Extensions component but do not disclose which policy check is bypassed or which operation exposes process memory. Exploitation requires convincing a user to install a malicious Chrome extension; the documented consequence is memory disclosure, with no reported write or service-interruption capability.
The record
- CVE
- CVE-2025-12436
- Published
- Nov 10, 2025
- Updated
- Nov 10, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-306, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 10, 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=142.0.7444.59 <142.0.7444.59
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