dbcve.org
ChromeWeb browser · Google

CVE-2025-1006

HIGH · 8.8 CVSS v3.1 Published 2025-02-19
Fix available
A fix is available. Upgrade to 133.0.6943.126 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 Network in Google Chrome prior to 133.0.6943.126 allowed a remote attacker to potentially exploit heap corruption via a crafted web app. (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

Use-after-free vulnerability in Chrome's Network component allows a remote attacker to potentially exploit heap corruption via a crafted web app. The flaw exists in versions prior to 133.0.6943.126 and could allow arbitrary code execution or memory corruption.

MitigationUpdate Google Chrome to version 133.0.6943.126 or later. Organizations should deploy the browser update through their patch management systems and verify completion across all 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:< 133.0.6943.126

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. Locate Chrome installation directory
    Check common installation paths: Windows typically installs to C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\. On macOS, check /Applications/Google Chrome.app. On Linux, check /opt/google/chrome or /usr/bin/google-chrome.
    Affected if Chrome is installed in any of these standard locations
  2. Find Chrome version file or executable
    In the Chrome Application folder, locate chrome.exe (Windows), Google Chrome (macOS), or google-chrome (Linux). On Windows, the version is also stored in the installer manifest or can be retrieved via Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Chrome executable or version registry entry exists on the system
  3. Retrieve installed Chrome version
    Run 'chrome.exe --version' from the command line, or on Windows right-click chrome.exe, select Properties, and check the Details tab for Product Version. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version'. On Linux, run 'google-chrome --version'.
    Affected if Command returns a version number (for example: 133.0.6943.101 or 132.0.6788.200)
  4. Compare version against affected range
    Compare the installed version number to 133.0.6943.126. Parse all four version components (133.6943.126 is the minimum safe version). If any component is lower (133 < 133, or 6943 < 6943, or 126 < 126), the installed version is vulnerable.
    Affected if Installed version is less than 133.0.6943.126 (for example, 133.0.6943.100, 132.0.6788.200, or 131.0.5000.0)

User is affected if Google Chrome is installed and its installed version number is less than 133.0.6943.126.

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 133.0.6943.126 or later
Fixed in 133.0.6943.126
Interim mitigation

Update Google Chrome to version 133.0.6943.126 or later. Organizations should deploy the browser update through their patch management systems and verify completion across all managed endpoints.

Recommended fix High confidence

Chrome 133.0.6943.126 or later

  1. 1. Open Google Chrome and navigate to Help > About Google Chrome to verify the current version
  2. 2. If the version is below 133.0.6943.126, download the latest stable Chrome version from the official website (chrome.google.com) or wait for automatic update
  3. 3. Install the update by running the downloaded installer
  4. 4. Restart Google Chrome to complete the update
  5. 5. Verify the version now shows 133.0.6943.126 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1006 — 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-1006 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