ChromeWeb browser · Google
CVE-2025-6554
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedType confusion in V8 in Google Chrome prior to 138.0.7204.96 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceType confusion vulnerability in Chrome's V8 JavaScript engine allows a remote attacker to perform arbitrary read/write operations via a crafted HTML page. This occurs when the engine incorrectly handles object types, leading to memory corruption that can be exploited for code execution or data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 138.0.7204.96< 138.0.7204.92CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Chrome executable and versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Note the version number displayed.Affected if Version displayed is below 138.0.7204.92 for Stable channel or below 138.0.7204.96 for other release channels
-
Confirm V8 JavaScript engine is presentVerify the Chrome installation includes the V8 engine by checking for the v8.dll or libv8.so library file in the Chrome installation directory.Affected if V8 engine component is present (this is standard in all Chrome installations, confirming the vulnerable component exists)
-
Verify no enterprise policy blocks JavaScriptCheck if group policy or enterprise management has disabled JavaScript. In Chrome, navigate to chrome://settings/content/javascript or check local computer policy (gpedit.msc) under Administrative Templates > Google Chrome > Content Settings.Affected if JavaScript is enabled (V8 must be active for the vulnerability to be exploitable)
User is affected if their installed Google Chrome version is below 138.0.7204.92 (Stable) or 138.0.7204.96 (other channels) and JavaScript execution is permitted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped138.0.7204.92138.0.7204.96
Update Google Chrome to version 138.0.7204.96 or later to patch the V8 type confusion vulnerability.
Chrome 138.0.7204.96 or later
- Check the current Chrome version by navigating to chrome://settings/help or selecting Chrome menu > Settings > About Chrome
- Download Google Chrome version 138.0.7204.96 or later from the official Chrome download page (chrome.google.com)
- Install the updated version of Chrome
- Restart Chrome to complete the installation
- Verify the version by checking chrome://settings/help - it should show version 138.0.7204.96 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6554 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6554 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data