ChromeWeb browser · Google
CVE-2025-11205
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 · uneditedHeap buffer overflow in WebGPU in Google Chrome prior to 141.0.7390.54 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 confidenceA heap buffer overflow vulnerability exists in Google Chrome's WebGPU implementation prior to version 141.0.7390.54. An attacker who has already compromised the renderer process can exploit this flaw through a crafted HTML page to achieve heap corruption, potentially leading to arbitrary code execution.
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
< 141.0.7390.54CVSS 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.
-
Determine Google Chrome installation and versionOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' or 'chrome --version' from command line. Record the displayed version number.Affected if The installed version is less than 141.0.7390.54 (for example, 141.0.7390.1 or earlier).
-
Verify WebGPU is enabled in the browserNavigate to chrome://flags/#enable-webgpu in the Chrome address bar. Check whether the 'Enable WebGPU' flag is set to Enabled or Default.Affected if WebGPU is explicitly enabled (not set to Disabled), as the vulnerability exists in the WebGPU implementation itself.
-
Check for renderer process indicatorsOpen Chrome Task Manager (Shift+Esc) while running a WebGPU-enabled page. Look for any unusual or unexpected renderer processes exhibiting abnormal behavior.Affected if Any unexpected renderer processes are observed, as the CVE assumes an already-compromised renderer process.
A user is affected if their installed Chrome version is below 141.0.7390.54 AND WebGPU is enabled in the browser settings.
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 · scoped141.0.7390.54
Update Google Chrome to version 141.0.7390.54 or later. In enterprise environments, ensure automated browser update policies are enforced and patch deployment covers all affected endpoints.
Chrome 141.0.7390.54 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version shown is earlier than 141.0.7390.54, click 'Update Google Chrome' button if visible
- Restart Chrome to complete the update process
- Verify the version is now 141.0.7390.54 or later by revisiting chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11205 — 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-2025-11205 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