dbcve.org
ChromeWeb browser · Google

CVE-2026-8000

HIGH · 8.8 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 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
Insufficient validation of untrusted input in ChromeDriver in Google Chrome on Windows prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Low)

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

Insufficient validation of untrusted input in ChromeDriver on Windows allows remote attackers to achieve arbitrary code execution through a specially crafted HTML page. The vulnerability exists due to missing input sanitization in ChromeDriver's web request handling, enabling malicious HTML to trigger unsafe operations.

MitigationUpdate Google Chrome and ChromeDriver to version 148.0.7778.96 or later to patch the input validation 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.96

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. Identify ChromeDriver presence on Windows
    Check if chromedriver.exe exists on the system or is running: Open Task Manager, look for 'chromedriver' in processes, or run 'where chromedriver' in Command Prompt
    Affected if ChromeDriver is installed and running on Windows systems with vulnerable Chrome versions
  2. Determine installed Google Chrome version
    Open Chrome, go to Settings > About Chrome, or navigate to chrome://version/, or run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' in Command Prompt
    Affected if The displayed version number is lower than 148.0.7778.96 (for example, 147.x.x.x or earlier)
  3. Check ChromeDriver remote access configuration
    Inspect chromedriver logs or configuration files for '--allowed-ips' or '--allowed-origins' flags that permit external access, or check if ChromeDriver is bound to 0.0.0.0 rather than localhost
    Affected if ChromeDriver is configured to accept remote connections from non-localhost sources
  4. Verify webdriver.http.server.enabled or similar remote config
    Look for ChromeDriver command-line arguments in running processes using 'wmic process where "name='chromedriver.exe'" get commandline', or check for Selenium/WebDriver configuration files that expose ChromeDriver to network
    Affected if ChromeDriver HTTP server is exposed to network accessible IP addresses

The environment is affected if ChromeDriver is running on Windows with Google Chrome version below 148.0.7778.96 and ChromeDriver is network-accessible to remote attackers.

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.96 or later
Fixed in 148.0.7778.96
Interim mitigation

Update Google Chrome and ChromeDriver to version 148.0.7778.96 or later to patch the input validation vulnerability.

Recommended fix High confidence

Chrome 148.0.7778.96 or later

  1. Verify current Chrome version by navigating to chrome://settings/help in the browser address bar
  2. Download and install Chrome version 148.0.7778.96 or later from the official Google Chrome website (google.com/chrome)
  3. If using ChromeDriver programmatically, ensure ChromeDriver is updated to match the new Chrome version
  4. Restart Chrome and ChromeDriver services after the upgrade
  5. Verify the new version is installed by checking chrome://settings/help

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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