dbcve.org
ChromeWeb browser · Google

CVE-2026-8531

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 on Windows prior to 148.0.7778.168 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 confidence

Heap buffer overflow vulnerability in WebML (Web Machine Learning) component of Google Chrome on Windows prior to version 148.0.7778.168. A remote attacker can exploit this via a crafted HTML page to achieve heap corruption, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later on all Windows systems. Apply via organization patch management or manual update.

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. Verify Google Chrome is installed on Windows
    Open Command Prompt and run: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" or check for Chrome shortcut in Program Files
    Affected if Google Chrome is not found on the system, the vulnerability does not apply
  2. Determine installed Chrome version
    Open Chrome, go to Settings > About Chrome, or run: chrome://settings/help in the address bar, or use command: wmic datafile where "name='C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe'" get Version
    Affected if The displayed version number is lower than 148.0.7778.168
  3. Confirm operating system is Windows
    Run: systeminfo | findstr /B /C:"OS Name" or check system properties
    Affected if The operating system is Windows (the CVE specifically affects Windows builds of Chrome)
  4. Verify WebML component presence
    Chrome's WebML feature is automatically available when hardware acceleration is enabled. Check chrome://flags for 'WebML' or 'Machine Learning' related flags - the feature is built into Chrome but requires hardware support to be functional
    Affected if Chrome is running with WebML hardware acceleration enabled and version is below 148.0.7778.168

A user is affected if Google Chrome is installed on Windows and the installed version is lower than 148.0.7778.168, making the WebML component vulnerable to heap buffer overflow via crafted HTML pages.

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 on all Windows systems. Apply via organization patch management or manual update.

Recommended fix High confidence

Chrome 148.0.7778.168 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Settings' from the dropdown menu
  4. Click 'About Chrome' in the left sidebar
  5. Chrome will automatically check for updates; if an update is available, it will begin downloading
  6. Once the update to version 148.0.7778.168 or later is downloaded, click 'Restart' to apply the update
  7. Verify the update was successful by returning to 'About Chrome' and confirming the version number

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
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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