dbcve.org
ChromeWeb browser · Google

CVE-2026-13843

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 8 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 validation of untrusted input in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 sandbox escape vulnerability in Google Chrome for iOS versions prior to 150.0.7871.47. An attacker who has already compromised the renderer process (e.g., through a separate vulnerability) can exploit insufficient input validation in Chrome for iOS to escape the sandbox isolation by tricking the user into visiting a crafted HTML page. The vulnerability is rated High severity in Chromium and has a CVSS score of 9.6.

MitigationUpdate Google Chrome for iOS to version 150.0.7871.47 or later. Organizations should verify end-user devices have the updated browser version and consider enterprise mobility management tools to enforce updates.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
    Open the iOS Settings app and scroll through the list of installed applications. Verify that Google Chrome for iOS appears in the list of apps.
    Affected if Chrome for iOS is not present on the device - the vulnerability does not apply to other browsers or Chrome on other platforms.
  2. Locate the version number in Chrome for iOS
    Open the Chrome for iOS app. Tap on the profile icon in the bottom-right corner, then tap on 'Chrome' or the settings gear icon. Scroll down and tap on 'Chrome' again to access version information. Alternatively, check in iOS Settings by finding Chrome in the app list and tapping on it.
    Affected if Unable to locate version information - the version must be verified to determine if it falls within the affected range.
  3. Compare installed version to affected threshold
    Identify the full version number displayed (for example: 150.0.7871.x or earlier). Compare this numeric version against 150.0.7871.47. Any version lower than 150.0.7871.47 is within the affected range.
    Affected if The installed version is less than 150.0.7871.47 - the device is running a vulnerable version of Chrome for iOS.
  4. Verify Chrome update availability
    In Chrome for iOS, navigate to the Chrome settings menu and look for an 'Update Chrome' option. If an update is available, it indicates the current version is outdated. Additionally, check the iOS App Store for Chrome updates.
    Affected if An update is available - this confirms the current installed version is below the patched release.

A device is affected if Google Chrome for iOS is installed with a version number lower than 150.0.7871.47.

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 verify end-user devices have the updated browser version and consider enterprise mobility management tools to enforce updates.

Recommended fix High confidence

Chrome for iOS version 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 apps
  3. Tap the Update button next to Google Chrome if version 150.0.7871.47 or later is available
  4. Alternatively, go to Settings > App Store and enable Automatic Downloads to receive future updates automatically
  5. After updating, verify the version by opening Chrome, tapping the three dots menu, scrolling to Settings, and checking the version number

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-13843 — 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-13843 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