dbcve.org
ChromeWeb browser · Google

CVE-2026-11270

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Inappropriate implementation in UI 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: 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 confidence

A UI implementation flaw in Google Chrome on Android prior to version 149.0.7827.53 allows a remote attacker to leak cross-origin data through a crafted HTML page. This is a client-side browser vulnerability affecting Android devices.

MitigationUpdate Google Chrome for Android to version 149.0.7827.53 or later on all affected 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
Affected:< 149.0.7827.53

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Chrome for Android is installed
    On the Android device, open Settings > Apps and locate Google Chrome in the app list. If Chrome is not present or if a different browser (e.g., Samsung Internet, Firefox) is used, this CVE does not apply.
    Affected if Chrome for Android is not installed or a different browser is in use
  2. Open Chrome version information
    Open the Chrome app on the Android device. Tap the three-dot menu in the top right, select Help, then tap About Chrome. The version number will be displayed on this screen.
    Affected if Unable to access the About Chrome page in the app
  3. Extract the installed version number
    Locate the version string shown in the About Chrome screen (for example: 149.0.7827.52 or earlier). Record the full version number including the build component.
    Affected if No version number is displayed or the page cannot be loaded
  4. Compare against the affected version range
    Compare your recorded version number to 149.0.7827.53. Versions are compared numerically where each segment (149, 0, 7827, XX) is evaluated in sequence.
    Affected if Your installed version is less than 149.0.7827.53 (for example: 148.x.x.x, 147.x.x.x, or any version starting with a number lower than 149 in the first position)

You are affected if Chrome for Android is installed and the version shown in About Chrome is numerically lower than 149.0.7827.53.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome for Android to version 149.0.7827.53 or later on all affected devices.

Recommended fix High confidence

Chrome for Android version 149.0.7827.53 or later

  1. Open the Google Play Store app on your Android device
  2. Search for "Google Chrome" or "Chrome"
  3. Tap "Update" if an update is available; if you don't see an update button, Chrome is already up to date
  4. Alternatively, open Chrome > tap the three-dot menu > Help & Feedback > About Chrome to check for and install updates
  5. After updating, verify the version by going to chrome://version to confirm version 149.0.7827.53 or later is installed
Caveat Standard Chrome updates have minimal breaking changes;极少数旧网站可能因安全策略变更出现兼容性问题

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11270 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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