ChromeWeb browser · Google
CVE-2026-11148
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 Payments in Google Chrome on Android prior to 149.0.7827.53 allowed a local 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 the Payments component of Google Chrome on Android prior to version 149.0.7827.53 allows a local attacker with craft HTML page to bypass same-origin policy protections and leak cross-origin data. This is a client-side vulnerability affecting only Android devices.
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.
-
Verify the device is running AndroidCheck the device operating system. On the Android device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device is not running Android - this vulnerability only affects Chrome on Android
-
Check Google Chrome version on AndroidOpen Chrome app, tap the three dots menu > Help and feedback > Help > Chrome version, or navigate to chrome://version in the address bar. Alternatively, check via ADB shell with 'dumpsys package com.android.chrome | grep versionName'Affected if Unable to determine Chrome version - cannot assess vulnerability status
-
Compare installed Chrome version against vulnerable rangeReview the Chrome version number found in the previous step. The affected version range is any version less than 149.0.7827.53Affected if Chrome version is less than 149.0.7827.53 - the device is vulnerable to the Same-Origin Policy bypass in the Web Payments API
A user is affected if they are running Google Chrome on an Android device with a version lower than 149.0.7827.53, as the SOP bypass in the Payments component only applies to Chrome on Android in those versions.
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. Organizations should ensure mobile devices receive automatic browser updates through MDM or enterprise mobility policies.
Chrome 149.0.7827.53 or later on Android
- Open the Google Play Store on your Android device
- Search for Google Chrome or navigate to Chrome in your installed apps
- Tap Update to install Chrome version 149.0.7827.53 or later
- Alternatively, enable auto-updates in Play Store settings to receive future security updates automatically
- After updating, verify the version by navigating to chrome://version in the browser address bar
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-11148 — 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-11148 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