dbcve.org
ChromeWeb browser · Google

CVE-2026-11047

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Inappropriate implementation in Base 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 confidence

Inappropriate implementation in Chrome's Base component on Windows prior to version 149.0.7827.53 allowed a remote attacker who had already compromised the renderer process to potentially escape the sandbox via a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later; enterprise environments should verify complete deployment across all Windows clients.

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
Affected:< 149.0.7827.53

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Chrome is installed on Windows
    Check for Google Chrome installation by looking for chrome.exe in typical installation directories (e.g., C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\) or by running 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Chrome*"}' in PowerShell
    Affected if Chrome is not installed on the Windows system, then this vulnerability does not apply
  2. Determine installed Chrome version on Windows
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://settings/help, or run 'reg query "HKLM\SOFTWARE\Google\Chrome\BLBeacon" /v version' in Command Prompt
    Affected if Unable to determine the installed version - further manual verification needed
  3. Compare installed version against affected range
    Review the version number obtained from the previous step and compare it to the affected range: versions prior to 149.0.7827.53 on Windows are vulnerable
    Affected if Installed Chrome version is less than 149.0.7827.53 on Windows - the system is potentially affected by this sandbox escape vulnerability
  4. Confirm Windows platform
    Verify the operating system is Windows by checking system properties or running 'winver' or 'systeminfo' in Command Prompt
    Affected if The system is not running Windows - this specific vulnerability does not apply as it targets Chrome on Windows only

The environment is affected if Google Chrome for Windows is installed with a version lower than 149.0.7827.53.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later; enterprise environments should verify complete deployment across all Windows clients.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome on Windows
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 149.0.7827.53 or later
  6. Restart Google Chrome to complete the update

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
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11047 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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