ChromeWeb browser · Google
CVE-2026-11097
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 WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data 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 confidenceInappropriate implementation in Android WebView allows a remote attacker to leak cross-origin data via a crafted HTML page. This bypasses same-origin policy protections, enabling unauthorized data access between different origins within the WebView context.
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.
-
Check Google Chrome browser version on AndroidOpen Chrome app, tap the three-dot menu, go to Settings > About Chrome, and note the version number displayedAffected if The displayed version is lower than 149.0.7827.53
-
Check Android System WebView versionGo to Settings > Apps > Android System WebView and view the version informationAffected if The WebView version is lower than 149.0.7827.53 and the app uses WebView to load cross-origin content
-
Identify if your app uses WebView to load external contentSearch your application code for android.webkit.WebView usage and any loadUrl or evaluateJavascript calls that handle sensitive dataAffected if Your application uses WebView to load content from multiple origins and the underlying WebView component is below version 149.0.7827.53
-
Check WebView package version programmaticallyUse PackageManager to query WebView package version: getPackageManager().getPackageInfo("com.google.android.webview", 0).versionNameAffected if The returned version code is less than 149.0.7827.53
You are affected if Google Chrome or Android System WebView installed on the device is version 149.0.7827.53 or lower and the WebView loads cross-origin content.
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 Android to version 149.0.7827.53 or later to patch the WebView vulnerability.
Chrome 149.0.7827.53 or later for Android
- Open Google Play Store on the Android device
- Search for "Google Chrome" or "Chrome"
- Tap on Google Chrome from the search results
- If an update is available, tap the "Update" button
- Alternatively, ensure Chrome is set to auto-update: Open Chrome, go to Settings > About Chrome, and verify the version is 149.0.7827.53 or later
- Restart Chrome after updating to ensure the fix is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11097 — 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-11097 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