ChromeWeb browser · Google
CVE-2026-11011
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 · uneditedInsufficient policy enforcement in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation 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 confidenceGoogle Chrome's Password Manager had insufficient policy enforcement that allowed a compromised renderer process to bypass site isolation protections. This security boundary flaw could enable a remote attacker with renderer code execution to access password data across different origins via crafted HTML pages.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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.
-
Check if Google Chrome is installedOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' in terminal, or check Programs and Features on WindowsAffected if Google Chrome is present on the system
-
Determine installed Chrome versionLocate the version number displayed in chrome://version or the command output. Note the three-part version number (e.g., 149.0.7827.53)Affected if Version is below 149.0.7827.53 (e.g., 148.x.x.x or earlier)
-
Verify Password Manager is enabledNavigate to chrome://settings/passwords in Chrome. Check if 'Offer to save passwords' or 'Google Password Manager' toggle is enabledAffected if Password Manager is enabled (default state) - this is required for the vulnerability to be exploitable
-
Confirm site isolation settingsNavigate to chrome://flags/#site-isolation-trial-opt-out. Check if site isolation has been disabled or customizedAffected if Site isolation has been disabled or weakened - however note that the vulnerability allows bypassing these protections even when enabled
User is affected if Google Chrome version is below 149.0.7827.53 and Password Manager is enabled, as the vulnerability allows a compromised renderer process to bypass site isolation and access password data across origins.
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
Update Google Chrome to version 149.0.7827.53 or later to patch the insufficient policy enforcement in the Password Manager.
Chrome 149.0.7827.53 or later
- 1. Open Google Chrome browser
- 2. Click on the three-dot menu in the top-right corner
- 3. Navigate to Help > About Google Chrome
- 4. The browser will check for updates and automatically download Chrome version 149.0.7827.53 or later
- 5. Click 'Relaunch' to restart Chrome and apply 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
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-11011 — 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-11011 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