ChromeWeb browser · Google
CVE-2025-12428
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 142.0.7444.59 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 memory read/write operations by tricking a user into visiting a crafted malicious HTML page. The vulnerability exploits the JIT compilation process by causing the engine to misinterpret object types, bypassing memory safety checks.
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
< 142.0.7444.59CVSS 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 versionOpen Chrome and navigate to chrome://version, or on Windows check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome\DisplayVersion in the registryAffected if The displayed version number is lower than 142.0.7444.59
-
Verify Chrome is the affected componentConfirm the vulnerable component is the V8 JavaScript engine embedded in Google ChromeAffected if The software is Google Chrome and not another Chromium-based browser
-
Confirm browser is in active useVerify Chrome is installed and has been run on the system, as the vulnerability is triggered when a user visits a malicious webpageAffected if Chrome is installed and was recently used, creating potential exposure to crafted HTML pages
The system is affected if Google Chrome version is below 142.0.7444.59 and the browser is in active use, allowing remote attackers to trigger the type confusion via malicious web content.
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 · scoped142.0.7444.59
Update Google Chrome to version 142.0.7444.59 or later. Organizations should ensure endpoint management/patch management processes push browser updates to all users.
Chrome 142.0.7444.59 or later
- Open Google Chrome and navigate to Settings > About Chrome to check the current version
- If the version is below 142.0.7444.59, Chrome will automatically check for and prompt you to update to the latest version
- Click 'Update Google Chrome' if prompted and restart the browser
- Alternatively, download the latest Chrome version directly from the official Google Chrome website (google.com/chrome)
- Verify the version after update by checking Settings > About Chrome - it should show 142.0.7444.59 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12428 — 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-12428 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