ChromeWeb browser · Google
CVE-2026-11226
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 PreviewTab in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)
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 confidenceInsufficient policy enforcement in PreviewTab in Google Chrome on Android prior to version 149.0.7827.53 allows a remote attacker to bypass same origin policy by tricking users into specific UI gestures through a crafted HTML page.
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.
-
Identify the browser and platformCheck if Google Chrome is installed on an Android device. This vulnerability only affects Chrome on Android, not Chrome on iOS or desktop Chrome. Go to Settings > Apps > Chrome to confirm the browser and platform.Affected if The browser is Google Chrome running on Android OS
-
Check installed Chrome version on AndroidOpen Chrome on the Android device, tap the three-dot menu, go to Settings > About Chrome to view the current version number.Affected if The displayed version number is less than 149.0.7827.53 (for example, 149.0.7827.52 or earlier)
-
Confirm PreviewTab feature usageThe vulnerability exists in the PreviewTab component. While direct verification requires code analysis, users should be aware that this feature allows tab previews. The attack requires tricking users into performing specific UI gestures while viewing a crafted page.Affected if Chrome version is below 149.0.7827.53 and the user has PreviewTab functionality enabled (enabled by default on Android Chrome)
If Google Chrome on Android is installed with a version lower than 149.0.7827.53, the environment is affected by this Same Origin Policy bypass vulnerability in PreviewTab.
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 for Android to version 149.0.7827.53 or later to remediate this vulnerability.
Chrome 149.0.7827.53 or later for Android
- Open the Google Play Store app on your Android device
- Search for "Google Chrome" in the search bar
- If an update is available, tap the "Update" button next to Google Chrome
- Wait for the update to download and install completely
- Launch or restart Google Chrome to ensure the updated version is active
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11226 — 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-11226 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