dbcve.org
ChromeWeb browser · Google

CVE-2026-10009

HIGH · 7.5 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 →
82/100
Remediation priority · High
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
Integer overflow in Skia in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox 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

Integer overflow vulnerability in Skia (2D graphics library) in Google Chrome versions prior to 148.0.7778.216 allows a remote attacker who has already compromised the renderer process to achieve arbitrary code execution within the sandbox boundary via a specially crafted HTML page.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to patch the vulnerability; organizations should also ensure renderer process sandboxing is functioning correctly and consider browser update management policies.

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

CVSS:3.1/AV:N/AC:H/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. Find installed Google Chrome version
    Open chrome://version in the address bar or go to Help > About Google Chrome. The version number appears next to 'Google Chrome' at the top.
    Affected if The displayed version is less than 148.0.7778.216
  2. Check Chrome version from command line
    Run 'google-chrome --version' on Linux, 'chrome --version' on Windows via cmd, or 'grep -i google ~/Library/Application\ Support/Google/Chrome/Last\ Version' on macOS.
    Affected if The reported version number is lower than 148.0.7778.216 or 148.0.7778.215
  3. Identify Chrome channel (if using Canary/Beta/Dev)
    Navigate to chrome://version and look at the 'Channel' field, or check via Help > About Google Chrome where the channel is sometimes displayed.
    Affected if Running an older stable, beta, or dev channel build that has not yet received the 148.0.7778.216 update
  4. Assess exposure to untrusted HTML content
    Determine whether Chrome is used to browse untrusted websites, open HTML files from external sources, or rendered in embedded contexts (webviews, extensions with broad permissions).
    Affected if Chrome processes untrusted HTML without additional isolation layers (like sandboxing disabled via --no-sandbox flag)

You are affected if Google Chrome is installed at a version lower than 148.0.7778.216 and the browser processes potentially malicious HTML content from untrusted sources.

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 patch the vulnerability; organizations should also ensure renderer process sandboxing is functioning correctly and consider browser update management policies.

Recommended fix High confidence

Chrome version 148.0.7778.216 or higher

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Click 'Check for updates' or wait for Chrome to automatically check
  3. If version 148.0.7778.216 or higher is available, click 'Update Google Chrome'
  4. Restart Chrome to complete the update
  5. Alternatively, download the latest Chrome installer from the official Google Chrome website and reinstall

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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