dbcve.org
ChromeWeb browser · Google

CVE-2026-11061

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
100/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
Type Confusion in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape 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

Type confusion vulnerability in ANGLE (a graphics library abstraction layer used by Chrome for WebGL) allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability exists prior to Chrome 149.0.7827.53 and can potentially enable sandbox escape, allowing the attacker to break out of Chrome's security sandbox and execute code on the underlying system.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automatic browser updates are enabled and deploy the update through their patch management infrastructure.

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
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. Locate Google Chrome installation
    Check if Google Chrome is installed on the system by looking for Chrome in common installation paths (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows or /Applications/Google Chrome.app on macOS) or by searching for 'chrome' in installed programs.
    Affected if Google Chrome is installed on the system
  2. Determine installed Chrome version
    Open Google Chrome and navigate to chrome://version, or click Help > About Google Chrome. Record the version number displayed (e.g., 149.0.7827.53).
    Affected if The version displayed is less than 149.0.7827.53 (for example, 148.x.x.x or earlier)
  3. Verify ANGLE graphics layer is in use
    In Chrome, navigate to chrome://gpu and look for 'ANGLE' or 'WebGL' in the Graphics Feature Status section. ANGLE is typically enabled by default to support WebGL graphics.
    Affected if ANGLE or WebGL is listed as enabled (this confirms the vulnerable component is active)
  4. Compare against affected version range
    Take the version number obtained in step 2 and compare it numerically to 149.0.7827.53. Any version starting with 148 or lower, or any version that does not start with 149.0.7827.53 or higher, is in the affected range.
    Affected if Installed version is 149.0.7827.53 or lower

If Google Chrome is installed and the version is below 149.0.7827.53, the system is affected by this vulnerability.

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

Update Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automatic browser updates are enabled and deploy the update through their patch management infrastructure.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Check current Chrome version by navigating to chrome://settings/help or clicking Settings > About Chrome
  2. Update Chrome to version 149.0.7827.53 or later. Most systems will auto-update, but you can manually trigger an update by clicking 'Update Google Chrome' if prompted
  3. Restart the browser completely to apply the update
  4. Verify the fix by returning to chrome://settings/help and confirming the version is 149.0.7827.53 or newer
Caveat Standard Chrome updates have minimal breaking changes; however, some web compatibility or deprecated API behaviors may change

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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