ChromeWeb browser · Google
CVE-2026-11150
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 XML in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) 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 confidenceA Universal Cross-Site Scripting (UXSS) vulnerability in Google Chrome's XML parsing implementation allows a remote attacker to bypass same-origin policy and inject arbitrary scripts or HTML via a crafted HTML page. This affects Chrome versions prior to 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify installed Chrome browsersCheck for Google Chrome installation by looking for chrome.exe in standard installation paths (C:\Program Files\Google\Chrome\Application\ on Windows, /Applications/Google Chrome.app on macOS, or via package manager on Linux)Affected if Google Chrome is present on the system
-
Determine Chrome version numberOpen Google Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, navigate directly to chrome://settings/help in the address bar. Note the version number displayed (for example: 149.0.7827.53)Affected if Version shown is less than 149.0.7827.53 (such as 149.0.7827.50 or any earlier version)
-
Compare version against affected rangeCompare your installed version string to the affected threshold: any version below 149.0.7827.53 is vulnerable. Version 149.0.7827.53 and later are not affectedAffected if Installed version starts with a number less than 149, or equals 149 but with a build number below .53
A user is affected if Google Chrome is installed and the displayed 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
Update Google Chrome to version 149.0.7827.53 or later. Organizations should verify auto-update is enabled or push the update via enterprise deployment tools.
Chrome 149.0.7827.53 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome' to download and install the fixed version (149.0.7827.53 or later)
- Restart the browser 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
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11150 — 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-11150 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