ChromeWeb browser · Google
CVE-2026-11204
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 Signin in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to bypass navigation restrictions 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 navigation restriction bypass vulnerability in Google Chrome's sign-in flow on iOS allowed remote attackers to bypass navigation restrictions through crafted HTML pages. The issue stemmed from an inappropriate implementation in the signin component that failed to properly enforce navigation constraints.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Confirm you are using Google Chrome on iOSOpen the Chrome app and verify it is the Google Chrome browser running on an iOS device (iPhone or iPad). This vulnerability affects only the iOS version of Chrome, not Android, desktop, or other browsers.Affected if The browser is Google Chrome running on iOS
-
Check the installed Chrome iOS versionOpen Chrome > tap the three dots menu > tap Settings > scroll to and tap About Chrome. The version number displayed should be compared against 149.0.7827.53.Affected if The installed version is lower than 149.0.7827.53 (for example, 149.0.7827.40 or any earlier version)
-
Verify the signin component is presentThe vulnerability exists in Chrome's signin flow. This is typically present by default on Chrome iOS when a Google account can be added via Settings > Sign in to Chrome. The check confirms the affected component exists.Affected if Chrome iOS is capable of handling signin flows, which is the default state for most installations
A user is affected if they are running Google Chrome on iOS with a version lower than 149.0.7827.53 and the signin feature is available, which is the default configuration.
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 on iOS to version 149.0.7827.53 or later. Organizations should ensure managed devices have the latest Chrome version deployed via their mobile device management (MDM) solution.
Chrome iOS 149.0.7827.53
- Open the App Store on your iOS device
- Search for Google Chrome or locate it in your installed apps
- Tap Update to install the latest version of Chrome for iOS
- Alternatively, enable automatic app updates in Settings > App Store > Automatic Downloads to ensure you receive future security updates
- After updating, verify the Chrome version by navigating to chrome://version in the address bar to confirm you are running version 149.0.7827.53 or later
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-11204 — 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-11204 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