ChromeWeb browser · Google
CVE-2026-11631
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 Aura in Google Chrome on Windows prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
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 Chrome's Aura UI framework on Windows (versions prior to 149.0.7827.103). A remote attacker with an already-compromised renderer process can exploit this via crafted HTML to potentially escape the sandbox and execute code outside the browser's security context.
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.103CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Open Chrome version pageNavigate to chrome://version in the Chrome address bar and note the version number displayed next to 'Google Chrome'Affected if The version listed is lower than 149.0.7827.103
-
Check Chrome version via command lineOpen Command Prompt or PowerShell and run: chrome --version or locate chrome.exe in Program Files and run: chrome.exe --versionAffected if The displayed version is 148.x.x.x or any version below 149.0.7827.103
-
Verify operating systemConfirm the affected system is running Windows. Run 'winver' or check System Properties to confirm the OSAffected if The system is Windows AND Chrome version is below 149.0.7827.103 (this vulnerability only affects Windows)
-
Check About ChromeClick the three-dot menu in Chrome, select Help, then About Google Chrome. The version is displayed on that pageAffected if Version shown is 149.0.7827.102 or lower
You are affected if Chrome version is less than 149.0.7827.103 on a Windows workstation.
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.103
Upgrade Google Chrome to version 149.0.7827.103 or later on all Windows systems. This is a browser patch; no application code changes are required unless the client is building a Chromium-based browser.
Chrome 149.0.7827.103 or later
- 1. Open Google Chrome on the affected Windows system
- 2. Navigate to Chrome Settings (three-dot menu > Settings)
- 3. Click on 'About Chrome' in the left sidebar
- 4. Chrome will automatically check for and install the latest version
- 5. Ensure the installed version is 149.0.7827.103 or later
- 6. Restart the browser if an update was installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11631 — 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-11631 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