ChromeWeb browser · Google
CVE-2026-11004
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 · uneditedOut of bounds read in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory 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 confidenceThis is an out-of-bounds read vulnerability in ANGLE (a graphics layer used by Chrome to translate OpenGL ES calls) that allows a remote attacker who has already compromised the renderer process to read sensitive data from process memory beyond allocated buffer boundaries. The attack is delivered via a crafted HTML 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Determine installed Google Chrome versionNavigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' from command lineAffected if The version shown is earlier than 149.0.7827.53 (for example, 148.x.x.x or earlier)
-
Confirm Chrome is the installed browserVerify that the browser is Google Chrome rather than Chromium or another Chromium-based browser, as this CVE specifically affects Google ChromeAffected if The browser is Google Chrome and the version is below 149.0.7827.53
-
Verify ANGLE graphics layer is in useANGLE (Almost Native Graphics Layer Engine) is used for WebGL rendering. Check if WebGL is enabled in Chrome settings at chrome://settings, or inspect for WebGL usage in web contentAffected if WebGL is enabled and being used, combined with an affected Chrome version below 149.0.7827.53
-
Assess renderer process integritySince this vulnerability requires the renderer process to already be compromised, review for signs of renderer compromise such as unexpected extensions, unusual network behavior, or memory anomalies in browser processesAffected if The renderer process has been compromised AND Chrome version is below 149.0.7827.53 AND ANGLE/WebGL is in use
You are affected if you are running Google Chrome version below 149.0.7827.53 with ANGLE/WebGL enabled, and the renderer process has already been compromised by an attacker.
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
Update Google Chrome to version 149.0.7827.53 or later. Organizations should ensure automatic updates are enabled or deploy the patched version through their endpoint management systems.
Chrome 149.0.7827.53 or later
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Select 'Help' then 'About Google Chrome'
- Chrome will check for updates and automatically download version 149.0.7827.53 or later
- Click 'Relaunch' to apply the update
- Verify the update by returning to About Google Chrome and confirming the version is 149.0.7827.53 or higher
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
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 locallyCheck whether your project pulls in CVE-2026-11004 — 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-11004 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