ChromeWeb browser · Google
CVE-2026-11009
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 · uneditedUse after free in USB in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker 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 confidenceUse after free vulnerability in the USB component of Google Chrome on Windows prior to version 149.0.7827.53 allows a remote attacker to execute arbitrary code via a crafted HTML page and potentially escape the browser's sandbox containment.
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.
-
Confirm Google Chrome is installed on WindowsOpen Control Panel > Programs and Features, or check for Chrome in the Start menu. Alternatively, look for chrome.exe in typical installation paths such as C:\Program Files\Google\Chrome\Application\ or C:\Users\<username>\AppData\Local\Google\Chrome\Application\Affected if Google Chrome is present on the system
-
Retrieve the installed Chrome versionLaunch Google Chrome, click the three-dot menu > Help > About Google Chrome. The version number will be displayed on that page. Alternatively, right-click chrome.exe in the installation directory, select Properties, and check the Details tab for the product versionAffected if The displayed version is less than 149.0.7827.53
-
Verify the operating system is WindowsThis vulnerability specifically affects Windows. Confirm the affected system is running Windows by checking System Properties or running 'winver' commandAffected if The system is running Windows and Chrome version is below 149.0.7827.53
A user is affected if Google Chrome is installed on a Windows system and the installed version is lower than 149.0.7827.53
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 on all affected Windows endpoints. In enterprise environments, ensure automated patch deployment or group policy updates are pushed to end-user machines.
Chrome 149.0.7827.53 (Stable channel)
- Open Google Chrome on the affected Windows machine
- Click the three-dot menu icon in the upper-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for available updates
- If version 149.0.7827.53 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the update
- Verify the update by returning to About Google Chrome and confirming the version number 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
- Testing2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11009 — 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-11009 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