dbcve.org
ChromeWeb browser · Google

CVE-2026-10017

HIGH · 8.3 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
90/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
Out of bounds read in Headless in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 · high confidence

An out-of-bounds read vulnerability exists in Google Chrome's Headless mode prior to version 148.0.7778.216. A remote attacker who has already compromised the renderer process can exploit this vulnerability through a crafted HTML page to potentially escape the sandbox isolation. The vulnerability is classified as Medium severity by Chromium but received a CVSS score of 8.3 (High).

MitigationUpdate Google Chrome to version 148.0.7778.216 or later. Organizations using Headless Chrome in automated testing or web scraping applications should prioritize this update and verify that their Chromium-based tools (Puppeteer, Playwright, Selenium, etc.) are using the patched browser version.

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

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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
    Locate the Chrome executable on the system. On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome is not installed on the system.
  2. Determine the installed Chrome version
    Run the command 'google-chrome --version' on Linux/macOS, or right-click the Chrome executable, select Properties, and view the Details tab on Windows. Alternatively, open Chrome, navigate to chrome://settings/help, or run 'chrome --version' in Command Prompt on Windows.
    Affected if The installed version cannot be determined or Chrome is not found.
  3. Compare the installed version to the affected range
    Take the version number obtained from the previous step and compare it to 148.0.7778.216. Note that versions prior to this (such as 148.0.7778.0 through 148.0.7778.215) are affected.
    Affected if The installed version is less than 148.0.7778.216.
  4. Determine if Headless mode is in use
    Check if automated scripts, testing frameworks (such as Puppeteer, Selenium, Playwright), or cron jobs invoke Chrome with the --headless flag or use headless Chrome libraries. Review automation scripts and scheduled tasks for presence of --headless or --headless=new arguments.
    Affected if Headless mode is actively used and the Chrome version is below 148.0.7778.216.

A user is affected if Google Chrome with a version below 148.0.7778.216 is installed AND Headless mode is being used, as the vulnerability resides specifically in Chrome's Headless mode implementation.

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

Update Google Chrome to version 148.0.7778.216 or later. Organizations using Headless Chrome in automated testing or web scraping applications should prioritize this update and verify that their Chromium-based tools (Puppeteer, Playwright, Selenium, etc.) are using the patched browser version.

Recommended fix High confidence

Chrome version 148.0.7778.216 or later (stable channel)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current version is below 148.0.7778.216
  3. If an update is available, click 'Update Google Chrome' and wait for the download to complete
  4. Restart Chrome to apply the update
  5. After restart, verify the version is 148.0.7778.216 or higher via Settings > 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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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