dbcve.org
ChromeWeb browser · Google

CVE-2025-13632

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 143.0.7499.40 or later.
See remediation →
61/100
Remediation priority · Elevated
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
Inappropriate implementation in DevTools in Google Chrome prior to 143.0.7499.41 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (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 confidence

A flaw in Chrome's DevTools implementation allowed a malicious extension, once installed by a user, to potentially escape the browser's sandbox isolation. The attacker needed to first social-engineer the victim into installing the crafted malicious extension. This is a client-side browser vulnerability affecting versions prior to 143.0.7499.41.

MitigationUpdate Chrome to version 143.0.7499.41 or later. Additionally, enforce strict extension installation policies and educate users about the risks of installing untrusted extensions, as this attack requires user participation to install the malicious extension.

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:< 143.0.7499.40

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
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

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 Chrome version
    Navigate to chrome://settings/help or use 'About Google Chrome' in the Chrome menu to view the current version number
    Affected if The version listed is less than 143.0.7499.40 (e.g., 143.0.7499.39 or earlier)
  2. Review installed extensions
    Navigate to chrome://extensions/ and review the list of installed extensions
    Affected if Any extension is installed that was not intentionally added by your organization or was installed through social engineering
  3. Check extension installation policy
    On managed systems, check Group Policy settings under Computer Configuration > Administrative Templates > Google Chrome > Extensions for 'Extension installation settings'
    Affected if Extension installation is allowed or set to 'Allow all extensions' without restriction
  4. Verify Chrome channel
    Check if Chrome is running as a regular release, beta, or dev channel by viewing the version number
    Affected if Running a pre-release channel (Beta, Dev, Canary) that is older than the patched version 143.0.7499.41

You are affected if your Chrome version is below 143.0.7499.40 AND a malicious extension has been installed through social engineering, as the vulnerability enables sandbox escape from such extensions.

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

Update Chrome to version 143.0.7499.41 or later. Additionally, enforce strict extension installation policies and educate users about the risks of installing untrusted extensions, as this attack requires user participation to install the malicious extension.

Recommended fix High confidence

Chrome 143.0.7499.41

  1. 1. Open Google Chrome on your system
  2. 2. Navigate to Chrome menu > Help > About Google Chrome
  3. 3. Chrome will automatically check for updates
  4. 4. If an update is available, click 'Update Chrome'
  5. 5. Restart the browser to apply the update
  6. 6. Verify the version is 143.0.7499.41 or later by returning to Help > About Google Chrome

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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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