ChromeWeb browser · Google
CVE-2026-11052
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 · uneditedType Confusion in GPU in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceType confusion vulnerability in the GPU process of Google Chrome on Windows before version 149.0.7827.53. An attacker who has already compromised the renderer process can exploit this vulnerability via a crafted HTML page to potentially escape the browser sandbox. The GPU process runs with elevated privileges, making this a high-impact chained vulnerability.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Google Chrome is installed on WindowsCheck for chrome.exe in common installation paths: %ProgramFiles%\Google\Chrome\Application\chrome.exe or %LocalAppData%\Google\Chrome\Application\chrome.exe. Alternatively, query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome.Affected if Google Chrome is found to be installed on the system.
-
Determine installed Google Chrome versionOpen Chrome and navigate to chrome://version, or right-click chrome.exe in File Explorer, select Properties, and check the File version on the Details tab. The version number is displayed as the first line in chrome://version.Affected if Unable to retrieve the version number.
-
Compare version against the affected rangeCompare the installed version number (for example, 149.0.7827.53 or earlier like 128.0.6619.134) to the safe version 149.0.7827.53. Extract the four-part version number (major.minor.build.patch) and check if it is less than 149.0.7827.53.Affected if The installed version is less than 149.0.7827.53 (for example, 148.x.x.x, 147.x.x.x, or any earlier version).
A user is affected if Google Chrome for Windows is installed with any version prior to 149.0.7827.53, as the type confusion vulnerability in the GPU process can be exploited by an attacker who has already compromised the renderer process.
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. In enterprise environments, deploy the update via patch management or group policy to ensure all Windows workstations are patched.
Chrome 149.0.7827.53 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version number
- Chrome will automatically check for updates; if an update is available, click 'Update Google Chrome'
- Restart the browser to complete the update
- Confirm the version is 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
- 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-11052 — 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-11052 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