ChromeWeb browser · Google
CVE-2025-10585
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 140.0.7339.185 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 confidenceType confusion vulnerability in the V8 JavaScript engine in Google Chrome prior to version 140.0.7339.185 allows remote attackers to exploit heap corruption via malicious HTML pages. This arises from improper type handling in V8 leading to memory corruption that can be triggered by specially crafted JavaScript code embedded in HTML.
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
< 140.0.7339.185all versionsCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Google Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' (Linux), check file properties of chrome.exe (Windows), or Get-Info on Google Chrome.app (Mac)Affected if The displayed version is less than 140.0.7339.185
-
Confirm version format matches advisoryEnsure the version number format is complete (e.g., 140.0.7339.185) and not a shorter variant like 140.0.7339.184 or 139.x.x.xAffected if The version string starts with a number lower than 140, or starts with 140 but the full four-part version is below 140.0.7339.185
-
Verify V8 JavaScript engine is activeThis vulnerability affects the V8 engine which is always enabled in Chrome by default; no manual configuration requiredAffected if Google Chrome is running with standard V8 JavaScript engine (default behavior for all Chrome installations)
You are affected if your installed Google Chrome version is any version prior to 140.0.7339.185, as the type confusion in V8 can be triggered by visiting a specially crafted webpage.
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 · scoped140.0.7339.185
Update Google Chrome to version 140.0.7339.185 or later. Organizations should use endpoint management tools to verify all clients have applied the update.
140.0.7339.185
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 140.0.7339.185, Chrome will automatically check for updates; click 'Update Google Chrome' if available
- Restart Chrome to complete the update
- Alternatively, download the latest stable Chrome from https://www.google.com/chrome/ and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10585 — 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-10585 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