dbcve.org
ChromeWeb browser · Google

CVE-2026-7906

HIGH · 8.8 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
95/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 SVG in Google Chrome prior to 148.0.7778.96 allowed a remote attacker 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

Use After Free (UAF) vulnerability in Google Chrome's SVG rendering engine prior to version 148.0.7778.96 allows remote attackers to execute arbitrary code via a crafted malicious HTML page. Despite the sandbox containment, the high CVSS score (8.8) reflects reliable code execution capability.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later to patch the vulnerability. Organizations should deploy browser updates through their patch management 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Check installed Google Chrome version
    Open chrome://version in the Chrome address bar or click Help > About Google Chrome to view the full version number
    Affected if The displayed version number is lower than 148.0.7778.96 (e.g., 148.0.7778.95, 147.x.x.x, etc.)
  2. Verify Chrome version via command line
    On Windows, run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' or check the Chrome executable properties. On macOS, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString'. On Linux, run 'google-chrome --version' or 'chromium --version'
    Affected if The version returned is below 148.0.7778.96
  3. Confirm Chrome is actively used in the environment
    Check for installed Chrome instances via system inventory tools, endpoint detection systems, or by examining common installation paths: Windows: %ProgramFiles%\Google\Chrome\Application\chrome.exe, macOS: /Applications/Google Chrome.app, Linux: /usr/bin/google-chrome or /usr/bin/chromium
    Affected if Google Chrome or Chromium is installed with a version below 148.0.7778.96

If Google Chrome (or Chromium-based browsers) is installed with any version prior to 148.0.7778.96, the environment is affected by this UAF vulnerability in the SVG rendering engine.

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 vulnerability. Organizations should deploy browser updates through their patch management systems.

Recommended fix High confidence

Chrome version 148.0.7778.96 or later (stable channel)

  1. 1. Check current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
  2. 2. If the version is lower than 148.0.7778.96, download the latest stable Chrome from the official website at chrome.google.com
  3. 3. Install the update - Chrome will typically auto-update, but you can manually download and run the installer from the official Chrome download page
  4. 4. Restart Chrome after the update completes
  5. 5. Verify the version now shows 148.0.7778.96 or later by checking chrome://settings/help
Caveat Minimal risk - Chrome minor version updates are typically backward-compatible security patches; enterprise environments may want to test against internal web applications

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