dbcve.org
ChromeWeb browser · Google

CVE-2026-7951

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
Out of bounds write in WebRTC 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: Medium)

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

This is an out-of-bounds write vulnerability in Google's WebRTC (Web Real-Time Communication) component. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially allowing arbitrary code execution within the browser's sandboxed environment. The vulnerability affects Chrome versions prior to 148.0.7778.96.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management systems and verify complete coverage across all endpoints.

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 Chrome version
    Navigate to chrome://settings/help or enter chrome://version in the address bar to display the full version string including major, minor, build, and patch numbers
    Affected if The displayed version is less than 148.0.7778.96 (for example, 148.0.7778.95 or any earlier version)
  2. Verify Chrome channel
    Check if Chrome is installed via stable, beta, dev, or canary channel. On Windows, right-click the Chrome shortcut and select 'About Google Chrome'. On macOS, open Chrome and go to Chrome > About Google Chrome
    Affected if The channel is stable but the version is below 148.0.7778.96, or if using beta/dev/canary with version below the affected threshold
  3. Confirm WebRTC is enabled
    In Chrome settings, search for 'WebRTC' or navigate to chrome://flags/#enable-webrtc and verify the WebRTC feature is not disabled. WebRTC is typically enabled by default
    Affected if WebRTC is enabled (the default state), which is required for the vulnerable code path to be exercised

A user is affected if their Google Chrome version is earlier than 148.0.7778.96 and WebRTC remains in its default enabled state, allowing the crafted HTML page to trigger the out-of-bounds write during WebRTC processing.

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 remediate this vulnerability. Organizations should deploy browser updates through their patch management systems and verify complete coverage across all endpoints.

Recommended fix High confidence

Chrome 148.0.7778.96 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Alternatively, navigate to chrome://settings/help in the address bar
  3. Chrome will automatically check for updates
  4. If an update is available, click 'Update Google Chrome'
  5. Restart Chrome to complete the update
  6. Verify the version by returning to chrome://settings/help and confirming the version is 148.0.7778.96 or later
Caveat Chrome auto-updates typically have no breaking changes; however, some enterprise policies or legacy extensions may require testing after major version updates

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