dbcve.org
ChromeWeb browser · Google

CVE-2026-10919

HIGH · 8.3 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
90/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 ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 Chrome's ANGLE graphics library. A remote attacker who has already compromised the renderer process can exploit freed memory via a crafted HTML page to potentially escape Chrome's sandbox and execute code on the host system.

MitigationUpgrade Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automated browser updates are enabled and push the patch to affected 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:< 149.0.7827.53

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm Google Chrome is installed
    Check for Chrome executable: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /opt/google/chrome/chrome or via package manager.
    Affected if Chrome is not installed on the system - this CVE only affects Google Chrome, not Chromium or other browsers
  2. Retrieve installed Chrome version number
    Open Chrome, navigate to chrome://settings/help, or from command line run: chrome --version (Windows CMD), /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (macOS), google-chrome --version (Linux)
    Affected if Unable to determine version - cannot assess exposure
  3. Compare installed version to affected range
    Compare the retrieved version number to the affected range: versions prior to 149.0.7827.53 are vulnerable. Chrome versions are formatted as four numbers (e.g., 149.0.7827.53) - check if the first number is less than 149, or if it equals 149 but subsequent numbers are lower than 7827.53
    Affected if Installed version is less than 149.0.7827.53 - the system is within the affected version range and could be exploited if an attacker has already compromised the renderer process
  4. Verify ANGLE graphics layer is in use
    This vulnerability is in the ANGLE graphics abstraction layer. ANGLE is typically enabled automatically for WebGL content. To check: navigate to chrome://gpu in Chrome and look for ' ANGLE ' in the Graphics Feature Status section
    Affected if ANGLE is listed as in use or enabled - the vulnerable component is active; however, since exploitation requires a compromised renderer process first, this check confirms the attack surface exists

If Google Chrome is installed and its version is below 149.0.7827.53 with ANGLE enabled, the environment falls within the affected range for this CVE.

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 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Upgrade Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automated browser updates are enabled and push the patch to affected endpoints.

Recommended fix High confidence

149.0.7827.53 or later

  1. Verify current Chrome version by navigating to chrome://settings/help or using the Chrome menu > Help > About Google Chrome
  2. Download the latest stable version of Google Chrome from the official website (google.com/chrome) or use the browser's built-in update mechanism
  3. Install the update and restart the browser to ensure the vulnerable version is no longer in use
  4. For enterprise environments, deploy version 149.0.7827.53 or later via your software distribution tools
Caveat Chrome updates typically have minimal breaking changes; however, some legacy extensions or enterprise applications may have compatibility issues with 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-10919 — 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-10919 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