ChromeWeb browser · Google
CVE-2026-3915
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 WebML in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to perform an out of bounds memory read 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 WebML (Web Machine Learning) component allows remote attackers to perform out-of-bounds memory reads via a crafted HTML page. The vulnerability exists in versions prior to 146.0.7680.71.
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
< 146.0.7680.71CVSS 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.
-
Check installed Chrome versionNavigate to chrome://settings/help or use 'About Google Chrome' in the Chrome menu to view the installed version numberAffected if version is less than 146.0.7680.71
-
Verify WebML component availabilityNavigate to chrome://gpu or check if WebML API is accessible via chrome://flags/#enable-webmachine-learning. The WebML feature may be listed under ML TensorFlow integration or Machine Learning flags.Affected if WebML or Machine Learning features are enabled or accessible in the browser
-
Confirm browser is reachable by crafted contentThis is a remote attack via crafted HTML pages. If Chrome processes untrusted web content (standard browsing), the attack surface exists.Affected if browser processes arbitrary web content without additional sandboxing restrictions
User is affected if running Google Chrome version below 146.0.7680.71 and the WebML feature is accessible or enabled in the browser, as the heap buffer overflow occurs in that specific component.
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 · scoped146.0.7680.71
Update Google Chrome to version 146.0.7680.71 or later to remediate the vulnerability. Organizations should prioritize patching browser instances given the high CVSS score and remote attack vector.
Chrome 146.0.7680.71 or later
- 1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version.
- 2. If the installed version is earlier than 146.0.7680.71, Chrome will automatically check for updates. Click 'Update Google Chrome' if prompted.
- 3. If automatic update is not available, download the latest Chrome version from the official Google Chrome download page.
- 4. Restart the browser after the update completes to apply the fix.
- 5. Verify the version now shows 146.0.7680.71 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
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3915 — 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-2026-3915 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