ChromeWeb browser · Google
CVE-2026-11174
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 Site Isolation 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 confidenceThis is a Site Isolation bypass vulnerability in Google Chrome prior to version 149.0.7827.53. Site Isolation is a security feature that ensures pages from different origins are rendered in separate renderer processes to prevent cross-site attacks. The vulnerability allowed an attacker who had already compromised the renderer process to bypass this isolation mechanism using a crafted HTML page, potentially enabling further attacks such as accessing data from other origins.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 versionOpen Chrome, click the three-dot menu, select Help > About Google Chrome. The version number is displayed on this page. Alternatively, navigate to chrome://settings/help in the address bar.Affected if The displayed version is lower than 149.0.7827.53 (for example, 149.0.7827.52 or earlier).
-
Verify Site Isolation is enabledNavigate to chrome://flags/#site-isolation-trial-opt-out in the address bar. Check whether Site Isolation has been manually disabled by the user or administrator.Affected if Site Isolation is enabled (the default state) because this bypass only affects environments where Site Isolation is active as a security boundary.
-
Check for signs of renderer process compromiseReview Chrome's process logs or crash reports for unexpected renderer process crashes or unauthorized script injection. On Windows, check Event Viewer for Chrome-related crash events. Look for suspicious extensions or unusual bookmarks that could indicate HTML-based payload delivery.Affected if Evidence exists of a compromised renderer process or suspicious HTML content that could have triggered the bypass.
You are affected if Chrome version is below 149.0.7827.53 AND Site Isolation was enabled at the time of potential exposure to a compromised renderer.
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 ensure standard patch management processes are applied to deploy browser updates.
Chrome 149.0.7827.53 or later
- Open Chrome and navigate to chrome://version to check the current installed version
- If the version is below 149.0.7827.53, navigate to chrome://settings/help to check for updates
- Click 'Update Google Chrome' if an update is available, or manually download Chrome 149.0.7827.53 or later from the official Google Chrome website
- Restart Chrome after the update completes to apply the changes
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
- 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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11174 — 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-11174 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