dbcve.org
ChromeWeb browser · Google

CVE-2026-7987

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 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 · moderate confidence

Use-after-free vulnerability in Chrome's WebRTC implementation allows a remote attacker to execute arbitrary code via a crafted HTML page. The flaw exists in versions prior to 148.0.7778.96 and involves improper memory management where freed memory is accessed after deallocation.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later to patch the vulnerability.

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. Verify Google Chrome is installed
    Check for Chrome executable: On Windows look for chrome.exe in program files, on macOS look for Google Chrome.app, on Linux run 'which google-chrome' or check /usr/bin/google-chrome
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version number
    Navigate to chrome://version in the Chrome address bar, or run 'google-chrome --version' from command line, or check About Chrome in the Chrome menu
    Affected if The displayed version is earlier than 148.0.7778.96 (for example 148.0.7778.0, 147.x.x.x, etc.)
  3. Confirm WebRTC is enabled
    Navigate to chrome://webrtc-internals in Chrome. If the page loads and displays stats, WebRTC is active. Alternatively, check for WebRTC policy settings in chrome://settings or group policy configurations
    Affected if WebRTC is enabled (this is the default state for most Chrome installations)
  4. Check for suspicious WebRTC-related browser crashes
    Review Chrome crash reports in the Chrome crashpad directory (typically %LOCALAPPDATA%\Google\Chrome\User Data\Crashpad\reports on Windows, ~/Library/Application Support/Google/Chrome/Crashpad on macOS, or ~/.config/google-chrome/Crashpad on Linux)
    Affected if Recent crash reports reference WebRTC components or the libwebrtc library

You are affected if Google Chrome is installed with a version number lower than 148.0.7778.96 and WebRTC functionality is enabled (the default state).

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.

Recommended fix High confidence

Chrome 148.0.7778.96 or later

  1. Open Google Chrome browser
  2. Navigate to Settings > About Chrome (or enter chrome://settings/help in the address bar)
  3. Chrome will automatically check for available updates
  4. If an update is available, click 'Update Google Chrome' to download and install it
  5. Restart the browser after the update completes to apply the fix

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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