dbcve.org
ChromeWeb browser · Google

CVE-2026-13795

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

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 policy enforcement in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: High)

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

This is a navigation restriction bypass vulnerability in Google Chrome for iOS versions prior to 150.0.7871.47. A remote attacker can exploit insufficient policy enforcement in the browser to bypass navigation restrictions by tricking users into visiting a crafted HTML page.

MitigationUpdate Google Chrome for iOS to version 150.0.7871.47 or later. Organizations should ensure employees have auto-updates enabled for mobile browsers or push the update through MDM solutions.

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:< 150.0.7871.47

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 Google Chrome for iOS installation
    On iOS devices, check if Google Chrome is installed by looking for the Chrome app icon (red, yellow, green, and blue circle with a white center) on the device home screen or in the app library. Alternatively, check through mobile device management (MDM) software or an enterprise mobile inventory for the presence of the app.
    Affected if Google Chrome for iOS is installed on any iOS device in the organization's device inventory
  2. Determine installed Chrome version
    Open Google Chrome on the iOS device, tap the three-dot menu in the top-right, go to Settings, then scroll to the bottom where the version number is displayed. For bulk detection, use MDM software or Apple Configurator to query app metadata for version information.
    Affected if The installed version number cannot be determined or the version shown is lower than 150.0.7871.47
  3. Compare version against affected range
    Take the identified version number and compare it numerically against 150.0.7871.47. Any version that is less than 150.0.7871.47 (for example: 150.0.7871.46, 149.x.x.x, 148.x.x.x, etc.) is in the affected range.
    Affected if The installed version is 149.x.x.x or any version below 150.0.7871.47
  4. Check auto-update status
    On iOS devices, go to Settings > App Store > Automatic Downloads and verify if App Updates is enabled. Alternatively, check via MDM configuration profiles for update-related restrictions that may prevent automatic Chrome updates.
    Affected if Auto-updates are disabled or restricted, meaning the browser will not automatically receive the patched version

A user is affected if Google Chrome for iOS is installed and the installed version is less than 150.0.7871.47, leaving the navigation restriction bypass vulnerability exploitable.

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 150.0.7871.47 or later
Fixed in 150.0.7871.47
Interim mitigation

Update Google Chrome for iOS to version 150.0.7871.47 or later. Organizations should ensure employees have auto-updates enabled for mobile browsers or push the update through MDM solutions.

Recommended fix High confidence

Chrome for iOS 150.0.7871.47 or later

  1. Open the App Store on your iOS device
  2. Search for Google Chrome or locate it in your installed apps
  3. Tap Update to install Chrome for iOS version 150.0.7871.47 or later
  4. Ensure auto-updates are enabled for future security patches

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
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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