Arbitrary memory read and write via type confusion
Published Jun 30, 2025 · Updated Oct 21, 2025
Type confusion in V8 in Google Chrome before 138.0.7204.96 allows remote attackers to read and write memory via crafted HTML. Google identifies V8 as the locus but has not published the incompatible runtime types or faulty operation because bug details remain restricted. A user must load attacker-controlled HTML; successful exploitation crosses JavaScript memory-safety boundaries, and active exploitation is confirmed.
Summary
What happened
Type confusion in V8 in Google Chrome before 138.0.7204.96 allows remote attackers to read and write memory via crafted HTML. Google identifies V8 as the locus but has not published the incompatible runtime types or faulty operation because bug details remain restricted. A user must load attacker-controlled HTML; successful exploitation crosses JavaScript memory-safety boundaries, and active exploitation is confirmed.
The record
- CVE
- CVE-2025-6554
- Published
- Jun 30, 2025
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2025CVE publishedPublication date reported by the CVE source.
- Jul 2, 2025Exploitation reportedCISA Known Exploited Vulnerabilities Catalog entry
- Oct 21, 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=138.0.7204.96 <138.0.7204.96
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.
Reported exploitation
- CISA Known Exploited Vulnerabilities Catalog entryknown exploited catalog
- Google in-the-wild exploitation reportreported exploitation
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