dbcve.org
ChromeWeb browser · Google

CVE-2026-7918

HIGH · 8.3 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 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
Use after free in GPU in Google Chrome prior to 148.0.7778.96 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 · moderate confidence

Use-after-free vulnerability in the GPU component of Google Chrome allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox by exploiting a crafted HTML page. The vulnerability affects Chrome versions prior to 148.0.7778.96.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later to patch the use-after-free vulnerability in the GPU component.

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
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. Verify Google Chrome is installed
    Check for Chrome installation in common locations: Windows (C:\Program Files\Google\Chrome\Application\chrome.exe), macOS (/Applications/Google Chrome.app), or Linux (/usr/bin/google-chrome or /opt/google/chrome/google-chrome). On Windows, you can also check Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Chrome is not found on the system - not applicable
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or right-click the chrome.exe file and select Properties > Details to view the Version field. On Windows command line: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version. On macOS: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. On Linux: google-chrome --version
    Affected if Unable to determine version - cannot assess vulnerability
  3. Compare installed version against affected range
    Compare the detected version number to 148.0.7778.96. The vulnerability affects all versions prior to this (e.g., 148.0.7778.0, 147.x.x.x, 146.x.x.x, etc.). Note the exact version shown in chrome://version under "Browser" or "Version"
    Affected if Installed version is less than 148.0.7778.96 (e.g., 147.0.6095.134, 146.0.1234.56, etc.) - vulnerable
  4. Check if GPU hardware acceleration is enabled
    In Chrome, navigate to chrome://settings or chrome://settings/?search=hardware and locate "Hardware acceleration mode" or "Use hardware acceleration when available" under Advanced settings. Alternatively, inspect chrome://gpu for GPU-related status
    Affected if GPU hardware acceleration is enabled - the vulnerable GPU component code path is active; however, version check in step 3 takes precedence for determining if the vulnerability exists

User is affected if Google Chrome is installed with a version lower than 148.0.7778.96, regardless of GPU settings, since the vulnerability exists in the GPU component code of those versions.

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 to version 148.0.7778.96 or later to patch the use-after-free vulnerability in the GPU component.

Recommended fix High confidence

Chrome 148.0.7778.96 or later (stable release)

  1. Open Google Chrome on the target system
  2. Click the three-dot menu icon in the upper-right corner of the browser
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. The browser will automatically check for and download version 148.0.7778.96 or later
  6. Click 'Relaunch' to complete the update, or manually restart the browser
Caveat Standard Chrome stable releases typically have minimal breaking changes; updates primarily include security patches

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-7918 — 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-7918 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