ChromeWeb browser · Google
CVE-2025-12437
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 · uneditedUse after free in PageInfo in Google Chrome prior to 142.0.7444.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceUse after free vulnerability in Chrome's PageInfo component allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. Exploitation requires the victim to perform specific UI gestures, making it a user-assisted attack vector.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 in the address bar, or go to Menu > Help > About Google Chrome. Note the full version number displayed.Affected if The version number is less than 142.0.7444.59 (for example, 142.0.7444.58 or earlier)
-
Confirm the browser is Google ChromeVerify the application is Google Chrome specifically, not a Chromium-based alternative like Microsoft Edge, Brave, or Vivaldi. Check the application name in chrome://version or the browser window title.Affected if The browser is Google Chrome (not another Chromium-based product)
-
Verify PageInfo component is accessibleRight-click on any webpage and select View page info, or click the icon to the left of the URL in the address bar (lock, info, or warning icon). The PageInfo dialog should open.Affected if PageInfo dialog can be opened - this is the component containing the vulnerability and cannot be disabled
Environment is affected if installed Chrome version is below 142.0.7444.59 and the PageInfo feature is accessible to users, since exploitation requires a user to open PageInfo on a malicious page.
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
Upgrade Google Chrome to version 142.0.7444.59 or later to patch the vulnerability. Organizations should ensure browsers are updated through patch management processes.
Google Chrome 142.0.7444.59 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for and download updates
- Once the update to version 142.0.7444.59 or later is complete, click 'Relaunch' to restart the browser
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12437 — 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-12437 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