dbcve.org
ChromeWeb browser · Google

CVE-2026-11272

HIGH · 8.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Insufficient validation of untrusted input in Reading List in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform privilege escalation 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 · moderate confidence

Insufficient validation of untrusted input in the Reading List feature of Google Chrome on iOS prior to version 149.0.7827.53 allows a remote attacker to perform privilege escalation by tricking users into engaging specific UI gestures on a crafted HTML page.

MitigationUpdate Google Chrome on iOS to version 149.0.7827.53 or later. Organizations should ensure mobile devices receive browser updates through their MDM solution.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Google Chrome for iOS is installed
    Check the device for the Google Chrome app in the iOS App Library or on the home screen. On managed devices, check via Mobile Device Management (MDM) software or ask users to verify the app is present.
    Affected if Google Chrome for iOS is installed on the device
  2. Identify installed Chrome for iOS version
    Open the Chrome app, tap the three-dot menu, go to Settings, then scroll to the bottom where the version number is displayed. Alternatively, check via MDM enrollment or ask users to report the version shown in Settings > Chrome > Version.
    Affected if The version displayed cannot be determined or is below 149.0.7827.53
  3. Compare version against affected range
    The affected version range is any Google Chrome for iOS version prior to 149.0.7827.53. If the installed version starts with 149.x.x.x, verify the full version number is 149.0.7827.53 or later.
    Affected if The installed version is a three-part number less than 149.0.7827.53 (for example, 148.x.x.x) or is 149.x.x.x but below 149.0.7827.53
  4. Assess Reading List usage context
    The vulnerability affects the Reading List feature specifically. This feature is available by default in Chrome for iOS and requires no special configuration to be present. The flaw is triggered when users interact with crafted HTML pages.
    Affected if The device runs an affected Chrome for iOS version and users have access to the Reading List feature (default behavior).

A device is affected if Google Chrome for iOS is installed and the installed version is below 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 on iOS to version 149.0.7827.53 or later. Organizations should ensure mobile devices receive browser updates through their MDM solution.

Recommended fix Moderate confidence

Chrome iOS version 149.0.7827.53 or later

  1. Open the App Store on your iOS device
  2. Tap on your profile icon in the top right corner
  3. Scroll down to see available updates
  4. Find Google Chrome in the list of apps with pending updates
  5. Tap 'Update' next to Google Chrome to install the latest version
  6. Ensure the update completes successfully - the new version should be 149.0.7827.53 or later
  7. Alternatively, search for Google Chrome in the App Store and tap 'Update' if an update is available
Caveat Minimal risk - browser security updates typically do not introduce breaking changes; ensure you back up any critical data before updating

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11272 — 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-11272 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