dbcve.org
ChromeWeb browser · Google

CVE-2026-15902

HIGH · 8.8 CVSS v3.1 Published 2026-07-20
Fix available
A fix is available. Upgrade to 150.0.7871.128 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 4 weeks old

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 Cast in Google Chrome prior to 150.0.7871.128 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 vulnerability in the Cast component of Google Chrome allows a remote attacker to execute arbitrary code within the sandbox context via a specially crafted HTML page. The vulnerability affects versions prior to 150.0.7871.128.

MitigationUpdate Google Chrome to version 150.0.7871.128 or later to remediate 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:< 150.0.7871.128

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 if Google Chrome is installed
    On Windows: Check for chrome.exe in Program Files or Program Files (x86). On macOS: Check /Applications/Google Chrome.app. On Linux: Run 'which google-chrome' or 'which chromium-browser' in terminal.
    Affected if Google Chrome is not installed - the check does not apply
  2. Determine the installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' (Linux) / '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' (Windows) in terminal.
    Affected if Version cannot be determined - unable to assess exposure
  3. Compare version against the affected range
    Compare the installed version number to 150.0.7871.128. Any version lower than 150.0.7871.128 (e.g., 149.x.x.x, 148.x.x.x) is within the affected range.
    Affected if Installed version is less than 150.0.7871.128 - environment is affected
  4. Verify Cast component is accessible
    In Chrome, check if Cast functionality is available: look for the Cast icon in the toolbar, or navigate to chrome://settings/cast to see if casting features are accessible.
    Affected if Cast is enabled and accessible - the vulnerable component is present and exploitable; if Cast is completely disabled the attack surface may be reduced but version still determines exposure

The environment is affected if Google Chrome is installed with a version lower than 150.0.7871.128, regardless of Cast component status, as the vulnerable code exists in 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 150.0.7871.128 or later
Fixed in 150.0.7871.128
Interim mitigation

Update Google Chrome to version 150.0.7871.128 or later to remediate the vulnerability.

Recommended fix High confidence

Google Chrome 150.0.7871.128 or later

  1. Open Google Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is earlier than 150.0.7871.128, click 'Update Google Chrome' to download and install the latest version
  3. Restart the browser after the update completes to apply the security fix
  4. Verify the version now shows 150.0.7871.128 or later

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