ChromeWeb browser · Google
CVE-2026-11091
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 · uneditedInappropriate implementation in Dawn in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform out of bounds memory access 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 a memory safety vulnerability in Dawn, Google's WebGPU implementation in Chromium. A remote attacker can exploit a crafted HTML page to perform out-of-bounds memory access, potentially reading or corrupting memory beyond allocated buffers in the WebGPU rendering pipeline.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://version in the Chrome address bar and note the version number displayed under 'Google Chrome X.X.X', or run 'chrome --version' from command lineAffected if Version number is less than 149.0.7827.53
-
Verify WebGPU (Dawn) is accessibleNavigate to chrome://gpu in Chrome and look for the WebGPU status under the 'Graphics' section, or check if WebGPU API is available by visiting a WebGPU test siteAffected if WebGPU is listed as enabled or available (vulnerability requires WebGPU to be present and functional)
-
Confirm Chromium-based browser variantCheck if using Google Chrome specifically (not Chromium, Edge, or other variants) by checking chrome://version - the product name field should show 'Google Chrome'Affected if The browser is Google Chrome with version below 149.0.7827.53
You are affected if running Google Chrome version below 149.0.7827.53 with WebGPU enabled and able to render HTML content from untrusted sources.
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 unable to update immediately may consider disabling WebGPU support via enterprise policy as a temporary mitigation.
Chrome 149.0.7827.53 or later
- Open Google Chrome browser
- Navigate to Settings (three-dot menu) > Help > About Google Chrome
- Chrome will automatically check for updates and display the current version
- If the version is below 149.0.7827.53, click 'Update Google Chrome'
- Restart the browser to complete the update
- Alternatively, download the latest Chrome version directly from google.com/chrome and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11091 — 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-11091 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