ChromeWeb browser · Google
CVE-2025-8010
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.168 allowed a remote attacker to potentially exploit heap corruption 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 confidenceThis is a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. Type confusion allows an attacker to manipulate how the engine interprets object types, leading to heap corruption. A remote attacker can exploit this by tricking a user into visiting a specially crafted malicious HTML page, potentially leading to arbitrary code execution.
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.168CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check installed Chrome versionNavigate to chrome://settings/help in the Chrome browser, or click Help > About Google Chrome. The version number is displayed at the top of the page.Affected if The displayed version is lower than 138.0.7204.168 (e.g., 138.0.7204.100 or earlier).
-
Verify V8 engine presenceThe V8 JavaScript engine is built into Chrome and cannot be checked separately. This check is implicit - if Chrome is running, V8 is active.Affected if This is always true when Chrome is in use; the version check above determines vulnerability status.
-
Confirm Chrome is the browser in useIdentify if Google Chrome (not Chromium, Edge, or other Chromium-based browsers) is the primary browser. Check the application name in the title bar or under Help > About Google Chrome.Affected if The browser is Google Chrome specifically, as this CVE affects Google Chrome and not all Chromium-based browsers.
A user is affected if they are running Google Chrome version lower than 138.0.7204.168 and use the browser to visit untrusted websites, as the type confusion in V8 can be triggered by malicious HTML pages.
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.168
Update Google Chrome to version 138.0.7204.168 or later. Until the update is applied, exercise caution when visiting untrusted websites.
Chrome version 138.0.7204.168 or later
- Open Google Chrome and navigate to Help > About Google Chrome to trigger the automatic update check
- Wait for Chrome to download and install version 138.0.7204.168 or later
- Restart Chrome browser to complete the update
- Alternatively, download the latest Chrome version directly from the official Google Chrome website if automatic update is unavailable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8010 — 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-8010 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