ChromeWeb browser · Google
CVE-2026-11020
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 · uneditedInappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted XML file. (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 confidenceChrome extensions had an inappropriate implementation that allowed a remote attacker to leak cross-origin data by tricking a user into opening a crafted XML file. The vulnerability existed in the extensions component prior to version 149.0.7827.53.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Determine installed Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the current version number displayed on the pageAffected if The displayed version is lower than 149.0.7827.53 (for example, 148.x.x.x or earlier)
-
Verify Chrome channel and update statusGo to chrome://settings/help and check if the browser shows 'Update available' or displays a specific version under the channel (Stable, Beta, Dev, Canary)Affected if The browser is on an older channel or shows an update is available indicating the version is below 149.0.7827.53
-
Check extension usage contextReview whether Chrome extensions are actively installed or used by navigating to chrome://extensions and observing if any extensions are enabledAffected if Extensions are enabled and the Chrome version is below 149.0.7827.53, making the cross-origin leak applicable
You are affected if the installed Google Chrome version is lower than 149.0.7827.53 and extensions are enabled, as the vulnerability resides in the Extensions component for versions prior to this release.
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 remediate this vulnerability.
Chrome 149.0.7827.53 or later (stable channel)
- Open Chrome and navigate to Menu > Help > About Google Chrome to check current version
- If version is below 149.0.7827.53, Chrome will automatically check for updates - click 'Update Google Chrome' if available
- Restart Chrome to apply the update
- Alternatively, download the latest Chrome version from the official Google Chrome website (chrome.google.com)
- Verify the version is now 149.0.7827.53 or later by checking Menu > Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 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-11020 — 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-11020 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