ChromeWeb browser · Google
CVE-2026-11090
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 · uneditedUninitialized Use in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data 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 confidenceAn uninitialized memory use vulnerability in ANGLE (a graphics library used by Chrome for WebGL) prior to version 149.0.7827.53 allows a remote attacker to leak cross-origin data via a crafted HTML page. The flaw stems from reading uninitialized memory in the graphics rendering path, which could expose sensitive data from other origins to an attacker-controlled page.
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
< 149.0.7827.53CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or enter chrome://version in the address bar to view the installed version numberAffected if The displayed version is less than 149.0.7827.53
-
Verify WebGL is enabledNavigate to chrome://gpu and look for 'WebGL' in the Graphics Feature Status section. WebGL relies on the ANGLE library.Affected if WebGL is listed as 'Hardware accelerated' or enabled - this means ANGLE is active and the vulnerable code path can be reached
-
Confirm Chrome is used for web browsingThis vulnerability is triggered by visiting a malicious HTML page, so confirm the browser is used for general web accessAffected if The browser has network access and is used to render untrusted web content
You are affected if Google Chrome version is below 149.0.7827.53 and WebGL/ANGLE is enabled, as the uninitialized memory read occurs in the graphics layer when processing web content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.53
Upgrade Google Chrome to version 149.0.7827.53 or later. Until then, restrict WebGL usage and disable hardware acceleration in enterprise configurations as a defense-in-depth measure.
149.0.7827.53 or later
- Open Google Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is below 149.0.7827.53, Chrome should automatically download and install the update
- If automatic update does not trigger, download the latest Chrome version from the official website (google.com/chrome)
- After the update is installed, restart Google Chrome to apply the fix
- Verify the version now shows 149.0.7827.53 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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