dbcve.org
ChromeWeb browser · Google

CVE-2026-9974

HIGH · 8.3 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 →
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 write in GPU 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: 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

Out-of-bounds write vulnerability in Google Chrome's GPU component prior to version 148.0.7778.216 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a crafted HTML page.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later; in enterprise environments, deploy the update organization-wide through patch management systems to ensure all clients receive the fix.

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
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. Identify Chrome installation location
    On Windows: Check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\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 Chrome browser is installed on the system
  2. Retrieve installed Chrome version number
    On Windows: Right-click chrome.exe, select Properties, view Details tab for Product version, or run 'wmic datafile where "name='C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe'" get version' in Command Prompt. On macOS: Run 'mdls -name kMDItemVersion /Applications/Google\ Chrome.app' in Terminal. On Linux: Run 'google-chrome --version' or 'google-chrome-stable --version' in Terminal
    Affected if Unable to retrieve version indicates Chrome may not be properly installed
  3. Compare version against affected range
    Compare the retrieved version number to 148.0.7778.216. Note that versions 148.0.7778.215 and below are affected, including older stable releases
    Affected if Installed version is lower than 148.0.7778.216 (for example, 148.0.7778.200, 128.0.0.0, etc.)
  4. Verify Chrome is actively used
    Check if Chrome is set as default browser or has recent usage history. On Windows: Check Registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.html\UserChoice for default browser. Review recent browser activity logs if available
    Affected if Chrome is the default or frequently used browser, making the user potentially vulnerable

The user is affected if Google Chrome is installed with a version number lower than 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; in enterprise environments, deploy the update organization-wide through patch management systems to ensure all clients receive the fix.

Recommended fix High confidence

Chrome 148.0.7778.216 or later

  1. 1. Open Google Chrome browser
  2. 2. Click on the three-dot menu in the top-right corner
  3. 3. Navigate to Help > About Google Chrome
  4. 4. Chrome will automatically check for updates
  5. 5. If version 148.0.7778.216 or later is available, click 'Update Google Chrome'
  6. 6. Relaunch the browser to complete the update
  7. 7. Verify the update by returning to Help > About Google Chrome and confirming version 148.0.7778.216 or later is installed
Caveat Standard Chrome security update; minimal risk of breaking changes for typical users

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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