ChromeWeb browser · Google
CVE-2025-0997
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 Navigation in Google Chrome prior to 133.0.6943.98 allowed a remote attacker to potentially exploit heap corruption 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 confidenceA use-after-free vulnerability exists in the Navigation component of Google Chrome versions prior to 133.0.6943.98. The flaw allows a remote attacker to potentially exploit heap corruption by tricking users into installing a maliciously crafted Chrome Extension that triggers the UAF condition during navigation operations.
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
< 133.0.6943.98CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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, navigate to chrome://settings/help, or run 'google-chrome --version' from command lineAffected if Version number is lower than 133.0.6943.98
-
Identify Chrome distribution channelNavigate to chrome://settings/help and look for 'Update Chrome' button status or check if this is a stable/beta/dev channel buildAffected if Not running stable channel or update status shows outdated version
-
Review installed extensionsNavigate to chrome://extensions and list all enabled extensionsAffected if Any extension is installed, especially from non-trusted sources, as the flaw is triggered by malicious extensions
-
Check extension installation policyOn managed systems, check chrome://policy for ExtensionInstallForcelist, ExtensionInstallSources, or ExtensionInstallBlocklist policiesAffected if Policy allows installation from untrusted sources or no restrictive policy exists
-
Verify if extension sideloading is possibleCheck if users can manually load unpacked extensions (Developer mode) via chrome://extensions toggleAffected if Developer mode is accessible to regular users, allowing arbitrary extension loading
You are affected if your Chrome version is below 133.0.6943.98 AND you have any extensions installed or have the ability to install them.
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 · scoped133.0.6943.98
Upgrade Google Chrome to version 133.0.6943.98 or later. Additionally, review and restrict Chrome Extension installation policies to only allow extensions from trusted sources.
133.0.6943.98 or later
- Open Google Chrome and navigate to Help > About Google Chrome to check the current version
- If the version displayed is earlier than 133.0.6943.98, click 'Update Google Chrome' to download and install the latest version
- Restart Chrome after the update completes to apply the fix
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
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 locallyCheck whether your project pulls in CVE-2025-0997 — 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-0997 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