dbcve.org
ChromeWeb browser · Google

CVE-2026-13780

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.46 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 8 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
Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

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

A sandbox escape vulnerability exists in ANGLE (a graphics library used by Chrome for WebGL) due to insufficient validation of untrusted input. A remote attacker who has already compromised the renderer process can exploit this via a crafted HTML page to escape the sandbox and execute code at a higher privilege level. The vulnerability affects Chrome versions prior to 150.0.7871.47.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later. This is a client-side vulnerability; organizations should deploy the updated browser version enterprise-wide and ensure automatic updates are enabled.

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.46

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 installed Google Chrome version
    Open Chrome, navigate to chrome://version, or go to Settings > About Chrome to see the current version number
    Affected if The installed version is lower than 150.0.7871.46 (any version from 150.0.0.0 through 150.0.7871.45 is affected)
  2. Verify WebGL status in Chrome
    Visit a WebGL test page (such as webgl.org or chrome://gpu) and confirm WebGL is enabled or run chrome://gpu in the browser to see graphics feature status
    Affected if WebGL is enabled (ANGLE is used as the WebGL backend on Windows; the vulnerability exists when ANGLE processes untrusted WebGL input)
  3. Check Chrome renderer process exposure
    Review whether the Chrome instance has been accessed via remote debugging, compromised extensions, or malicious websites that could provide an attacker renderer process access
    Affected if The renderer process has been compromised or the browser has been exposed to untrusted WebGL content from remote attackers

You are affected if Chrome version is below 150.0.7871.46 AND WebGL is enabled AND an attacker has already gained renderer process access, but the primary check is simply whether your Chrome version is below 150.0.7871.46.

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.46 or later
Fixed in 150.0.7871.46
Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later. This is a client-side vulnerability; organizations should deploy the updated browser version enterprise-wide and ensure automatic updates are enabled.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

  1. Open Google Chrome browser
  2. Navigate to Chrome Menu > Help > About Google Chrome
  3. The browser will check for updates automatically
  4. If an update is available, click 'Update Google Chrome'
  5. Restart the browser to complete the update
  6. Verify the version by returning to Help > About Google Chrome and confirm the version is 150.0.7871.47 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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