dbcve.org
ChromeWeb browser · Google

CVE-2026-11111

HIGH · 8.1 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
88/100
Remediation priority · High
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
Out of bounds read in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform an out of bounds memory read 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 · high confidence

An out-of-bounds read vulnerability exists in ANGLE (a graphics abstraction layer used by Chrome) that allows a remote attacker to read memory outside allocated buffers by tricking users into visiting a crafted HTML page. This could potentially expose sensitive memory contents to the attacker.

MitigationUpgrade Google Chrome to version 149.0.7827.53 or later. As a defense-in-depth measure, disable hardware acceleration in Chrome settings to prevent ANGLE from being used.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
    Open Chrome and navigate to chrome://settings/help, or check for chrome.exe (Windows), Google Chrome.app (macOS), or google-chrome (Linux) in standard installation directories
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    In Chrome address bar, enter chrome://settings/help and note the version number displayed, or run 'google-chrome --version' from command line on Linux
    Affected if Version number shown is lower than 149.0.7827.53
  3. Confirm WebGL/ANGLE graphics feature is in use
    The ANGLE library is used internally by Chrome for WebGL rendering. Visit chrome://gpu and check if 'WebGL' is listed under 'Graphics Feature Status', or any website using WebGL will automatically utilize ANGLE
    Affected if WebGL is enabled and functional in the browser (ANGLE is used by default for WebGL on supported platforms)
  4. Compare version against affected range
    Compare the installed version from step 2 to the affected range: versions prior to 149.0.7827.53 are vulnerable
    Affected if Installed version is less than 149.0.7827.53

User is affected if Google Chrome is installed with a version lower than 149.0.7827.53 and WebGL/ANGLE graphics rendering is enabled (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 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. As a defense-in-depth measure, disable hardware acceleration in Chrome settings to prevent ANGLE from being used.

Recommended fix High confidence

149.0.7827.53

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Alternatively, click the three-dot menu in the top-right corner and select 'Help' > 'About Google Chrome'
  3. The browser will automatically check for updates and download version 149.0.7827.53 or later
  4. Click 'Relaunch' or 'Restart' to apply the update
  5. Verify the update was successful by returning to About Google Chrome and confirming the version is 149.0.7827.53 or newer

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
  • Testing1.0 h
  • Review / QA1.0 h
4.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-11111 — 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-11111 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