dbcve.org
ChromeWeb browser · Google

CVE-2026-7910

CRITICAL · 9.6 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
100/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 Views in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to bypass site isolation 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

Use after free vulnerability in Chrome's Views component that allows a remote attacker who has already compromised the renderer process to bypass site isolation via a crafted HTML page, potentially enabling further security bypasses.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later; ensure enterprise patch management processes deploy browser updates across affected systems.

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

CVSS:3.1/AV:N/AC:L/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
    On Windows: Look for Chrome in C:\Program Files\Google\Chrome\Application\ or check Start Menu. On macOS: Check /Applications/Google Chrome.app. On Linux: Check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome browser is installed on the system
  2. Determine the installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. The version number is displayed on that page.
    Affected if The displayed version number is less than 148.0.7778.96
  3. Confirm the Views component is in use
    The Views UI framework is used by default in standard Chrome installations for browser UI elements. No special configuration check is needed - if Chrome is running normally, Views is active.
    Affected if Chrome is running a standard build (not a specialized sandbox-less build)
  4. Verify renderer process context
    This vulnerability requires an already-compromised renderer process. Check Chrome's task manager (Shift+Esc) for any suspicious processes or unusual CPU/memory usage from renderer processes.
    Affected if Any renderer process shows unexpected behavior or the user has recently visited untrusted websites

A user is affected if they are running any version of Google Chrome below 148.0.7778.96 and have used the browser to visit untrusted websites, as the vulnerability can be triggered via a crafted HTML page.

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; ensure enterprise patch management processes deploy browser updates across affected systems.

Recommended fix High confidence

148.0.7778.96

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Chrome will automatically check for updates and display the current version
  3. If a newer version is available, click 'Update Google Chrome'
  4. Restart Chrome to apply the update
  5. Verify the update was successful by returning to Settings > Help > About Google Chrome and confirming version 148.0.7778.96 or later is installed

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