dbcve.org
ChromeWeb browser · Google

CVE-2025-2136

HIGH · 8.8 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 134.0.6998.88 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Inspector in Google Chrome prior to 134.0.6998.88 allowed a remote attacker 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 confidence

A use-after-free vulnerability in the Chrome DevTools Inspector component allows a remote attacker to exploit heap corruption via a malicious HTML page. The vulnerability exists in how the Inspector handles certain DOM elements or object references, leading to memory corruption that can be weaponized for code execution.

MitigationUpdate Google Chrome to version 134.0.6998.88 or later. Organizations should deploy browser updates through their patch management infrastructure and verify completion across managed endpoints.

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
Affected:< 134.0.6998.88

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Open Chrome, click the three-dot menu (top right), select 'Help', then 'About Google Chrome'. The version number is displayed on this page.
    Affected if The displayed version number is less than 134.0.6998.88 (e.g., 134.0.6998.87 or earlier)
  2. Verify Chrome version via command line
    On Windows, open Command Prompt and run: chrome --version OR navigate to the Chrome installation folder (typically C:\Program Files\Google\Chrome\Application\) and run: chrome.exe --version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if The returned version is lower than 134.0.6998.88
  3. Check if multiple Chrome installations exist
    Search for all Chrome executables on the system: on Windows, check C:\Program Files\Google\Chrome\Application\ and C:\Program Files (x86)\Google\Chrome\Application\; on macOS, check /Applications/ for any Chrome instances
    Affected if Any found Chrome installation has a version below 134.0.6998.88
  4. Inspect browser policy or managed settings
    On managed enterprise systems, check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome (Windows) or plist files (macOS) for version deferral policies that may allow older versions to persist
    Affected if Policy settings permit version 134.0.6998.88 or below to remain in use

A system is affected if any installed Google Chrome instance has a version number lower than 134.0.6998.88, as the use-after-free in the Inspector component exists in those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 134.0.6998.88 or later
Fixed in 134.0.6998.88
Interim mitigation

Update Google Chrome to version 134.0.6998.88 or later. Organizations should deploy browser updates through their patch management infrastructure and verify completion across managed endpoints.

Recommended fix High confidence

134.0.6998.88 or later

  1. Open Google Chrome on your system
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome' (or it may update automatically)
  7. Restart Chrome 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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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