dbcve.org
ChromeWeb browser · Google

CVE-2026-8509

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 148.0.7778.168 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Heap buffer overflow in WebML in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Critical)

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 · moderate confidence

Heap buffer overflow in WebML (Web Machine Learning) component of Google Chrome allows a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later to remediate the vulnerability.

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

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal, or access About Google Chrome from the Chrome menu
    Affected if Version number is less than 148.0.7778.168
  2. Confirm WebML API availability
    Open a Chrome tab and inspect whether the navigator.ml or WebML API is exposed by running 'console.log(navigator.ml)' in Developer Tools
    Affected if The WebML API (navigator.ml) is present and accessible in the browser context
  3. Check WebML experimental flags
    Navigate to chrome://flags/#enable-web-machine-learning and verify whether WebML is enabled or disabled
    Affected if WebML is set to Enabled or Default (typically enabled by default in affected versions)

User is affected if Chrome version is below 148.0.7778.168 and WebML is accessible or enabled in the browser

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

Update Google Chrome to version 148.0.7778.168 or later to remediate the vulnerability.

Recommended fix High confidence

Chrome 148.0.7778.168 or later

  1. 1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. 2. The browser will automatically check for updates
  3. 3. If an update is available, download and install version 148.0.7778.168 or later
  4. 4. Restart the browser to complete the update
  5. 5. Verify the installed version by returning to Settings > Help > About Google Chrome and confirming the version is 148.0.7778.168 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing1.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,450
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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