ChromeWeb browser · Google
CVE-2025-4096
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 HTML in Google Chrome prior to 136.0.7103.59 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 Google Chrome's HTML parsing component allows a remote attacker to corrupt heap memory via a specially crafted malicious HTML page. This could enable arbitrary code execution or complete system compromise.
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
< 136.0.7103.59CVSS 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 Chrome and navigate to chrome://version, or click Help > About Google Chrome. Record the version number displayed (e.g., 136.0.7103.58).Affected if The displayed version number is less than 136.0.7103.59 (e.g., 136.0.7103.58, 135.x.x.x, etc.)
-
Identify Chrome installation channelsCheck if multiple Chrome installations exist (Stable, Beta, Dev, Canary) by reviewing installed programs in Add or Remove Programs (Windows), Applications folder (macOS), or package manager (Linux).Affected if Any installed Chrome channel has a version below 136.0.7103.59
-
Verify HTML parsing is reachableConfirm the Chrome browser is actively used for web browsing. No specific configuration check is required as HTML parsing is a core default feature.Affected if Chrome with a version below 136.0.7103.59 is in regular use, as the vulnerability triggers when parsing specially crafted HTML pages.
You are affected if any installed Google Chrome version is below 136.0.7103.59 and the browser is used to render untrusted HTML content.
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 · scoped136.0.7103.59
Update Google Chrome to version 136.0.7103.59 or later. Organizations should deploy the patch through their patch management infrastructure and verify complete coverage across all managed endpoints.
Chrome 136.0.7103.59
- Open Google Chrome and click the three-dot menu icon in the upper right corner
- Select 'Help' from the dropdown menu, then click 'About Google Chrome'
- Chrome will automatically check for updates and display the current version
- If an update is available, Chrome will download it automatically. Click 'Relaunch' to apply the update
- After Chrome restarts, verify the version by returning to Help > About Google Chrome to confirm version 136.0.7103.59 or later is installed
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-4096 — 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-4096 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