ChromeWeb browser · Google
CVE-2025-0437
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 · uneditedOut of bounds read in Metrics in Google Chrome prior to 132.0.6834.83 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 an out-of-bounds read vulnerability in Google Chrome's Metrics component that exists prior to version 132.0.6834.83. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption that could be weaponized for 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
< 132.0.6834.83CVSS 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.
-
Verify Google Chrome is installedCheck for Chrome executable in common installation paths: Windows typically at C:\Program Files\Google\Chrome\Application\chrome.exe, macOS at /Applications/Google Chrome.app, or run 'which google-chrome' on LinuxAffected if Chrome is not present on the system
-
Determine the installed Chrome versionOn Windows, right-click chrome.exe and select Properties > Details to view the File Version; on macOS, right-click the app > Get Info; on Linux, run 'google-chrome --version' or 'google-chrome-stable --version' in terminalAffected if Unable to retrieve the version number
-
Compare against affected versionCompare your installed version to the vulnerable threshold 132.0.6834.83 - note that version numbers follow semantic ordering where 132.0.6834.83 represents major.minor.build.patchAffected if Installed version is lower than 132.0.6834.83 (for example, 131.0.6778.264 would be affected)
If Google Chrome is installed and the version is below 132.0.6834.83, the environment is affected by this out-of-bounds read vulnerability in the Metrics component.
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 · scoped132.0.6834.83
Update Google Chrome to version 132.0.6834.83 or later. Organizations should deploy browser updates through their patch management infrastructure and verify compliance.
Chrome 132.0.6834.83 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the upper right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for and download the latest version
- After the update to version 132.0.6834.83 or later is downloaded, click 'Relaunch' or restart the browser to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0437 — 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-0437 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