ChromeWeb browser · Google
CVE-2025-0999
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 · uneditedHeap buffer overflow in V8 in Google Chrome prior to 133.0.6943.126 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 confidenceHeap buffer overflow vulnerability in Chrome's V8 JavaScript engine allowing remote attackers to potentially exploit heap corruption via malicious HTML pages. The flaw exists in versions prior to 133.0.6943.126 and could lead to arbitrary 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
< 133.0.6943.126CVSS 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.
-
Determine installed Chrome versionOpen Google Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, navigate to chrome://version in the address bar. Note the full version number displayed.Affected if The displayed version number is lower than 133.0.6943.126
-
Verify V8 engine version (optional)In Chrome, open a new tab and type chrome://version to see if V8 version is listed in the details. The V8 version is embedded within Chrome and cannot be updated separately.Affected if The V8 version correlates to a Chrome version below 133.0.6943.126
-
Check if Chrome is up to date via policyIf managed by an organization, check with your IT administrator or endpoint management system to confirm whether Chrome update deployment is configured and current.Affected if The organization has not deployed Chrome version 133.0.6943.126 or later via patch management.
You are affected if your installed Google Chrome version is lower than 133.0.6943.126, as the heap buffer overflow in the V8 JavaScript engine only exists in earlier versions.
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.126
Update Google Chrome to version 133.0.6943.126 or later. Organizations should deploy the update via their patch management infrastructure.
Chrome 133.0.6943.126 or later
- Open Google Chrome and navigate to Menu > Help > About Google Chrome
- Chrome will automatically check for updates and display the current version
- If the version is lower than 133.0.6943.126, click 'Update Google Chrome' to download and install the fix
- Restart the browser after the update completes to apply the security patch
- Verify the update was successful by returning to About Google Chrome and confirming the version is 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
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0999 — 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-0999 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