dbcve.org
ChromeWeb browser · Google

CVE-2026-11275

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 Page Info in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions 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

A vulnerability in Chrome for Android's Page Info feature allowed a remote attacker who had already compromised the renderer process to bypass navigation restrictions using a crafted HTML page. The flaw was an inappropriate implementation that failed to properly enforce navigation controls in the Page Info UI.

MitigationUpdate Google Chrome for Android to version 149.0.7827.53 or later. Organizations should ensure managed Android devices have the latest Chrome version deployed.

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

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

  1. Identify if Chrome for Android is installed
    Open Settings > Apps on the Android device and look for Google Chrome in the app list, or check the Chrome app icon on the home screen or app drawer.
    Affected if Google Chrome for Android is present on the device
  2. Locate the installed Chrome version
    In Settings > Apps > Google Chrome, tap on 'App info' or 'About' to display the version number. Alternatively, open Chrome, tap the three dots menu, go to Settings, and scroll down to 'Chrome version' at the bottom.
    Affected if A version number is displayed in the app details
  3. Compare the version against the affected range
    Take the displayed version number (e.g., 149.0.7827.53) and compare it numerically to the first affected version. Any version LOWER than 149.0.7827.53 falls within the affected range.
    Affected if The installed version is less than 149.0.7827.53 (e.g., 148.x.x.x, 147.x.x.x, etc.)
  4. Verify the attack surface condition
    This vulnerability requires a previously compromised renderer process as a prerequisite. Check if the device has been exposed to potential renderer exploits or if it runs untrusted web content.
    Affected if The device runs Chrome with untrusted web content and the Chrome version is below 149.0.7827.53

If Google Chrome for Android is installed and its version is lower than 149.0.7827.53, the device is within the affected version range and could be exploited if the renderer process is compromised.

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. Organizations should ensure managed Android devices have the latest Chrome version deployed.

Recommended fix High confidence

Chrome for Android 149.0.7827.53 or later

  1. Open Google Play Store on your Android device
  2. Search for Google Chrome
  3. Tap Update to install the latest version of Chrome
  4. Alternatively, go to Settings > Apps > Google Chrome > Update (if available)
  5. Ensure the updated version is 149.0.7827.53 or later

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 / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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