dbcve.org
ChromeWeb browser · Google

CVE-2026-10021

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.215 / 148.0.7778.216 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 USB in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Medium)

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 the USB subsystem of Google Chrome allows a remote attacker to execute arbitrary code on the victim's machine via a crafted HTML page. This is a client-side code execution vulnerability in the browser's USB handling code.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to obtain the patched version. Organizations should deploy the browser update through their patch management infrastructure.

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.216< 148.0.7778.215

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 if Google Chrome is installed
    On Windows: Look for Chrome in Program Files or check Start Menu. On macOS: Check /Applications for Google Chrome.app. On Linux: Run 'which google-chrome' or check /usr/bin/google-chrome.
    Affected if Google Chrome is not installed on the system - no action needed.
  2. Determine installed Chrome version (Windows)
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number will be displayed on that page.
    Affected if Version displayed is less than 148.0.7778.216 (or 148.0.7778.215 for certain channels).
  3. Determine installed Chrome version (macOS)
    Open Chrome, click Chrome menu > About Google Chrome. Alternatively, right-click the app in Applications > Get Info, or run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if Version displayed is less than 148.0.7778.216.
  4. Determine installed Chrome version (Linux)
    Run the command: google-chrome --version OR chrome --version OR chromium --version depending on installation.
    Affected if Version displayed is less than 148.0.7778.216.
  5. Check for multiple Chrome installations
    Search for all Chrome executables: Windows - check Program Files, Program Files (x86), user profile folders. macOS - check /Applications and ~/Applications. Linux - check common bin directories.
    Affected if Any installed Chrome instance is found to be below version 148.0.7778.216.

A system is affected if Google Chrome is installed and the installed version number is below 148.0.7778.216.

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.215 / 148.0.7778.216 or later
Fixed in 148.0.7778.215148.0.7778.216
Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later to obtain the patched version. Organizations should deploy the browser update through their patch management infrastructure.

Recommended fix High confidence

Google Chrome 148.0.7778.216 or later (Stable channel)

  1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is below 148.0.7778.216, click 'Update Google Chrome' if the button is available, or download the latest version from the official Google Chrome download page at google.com/chrome
  3. Restart the browser after the update completes
  4. Verify the update by returning to Help > About Google Chrome and confirming the version is 148.0.7778.216 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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