dbcve.org
ChromeWeb browser · Google

CVE-2026-13872

CRITICAL · 9.1 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 Zero-click 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 WebAppInstalls in Google Chrome on Android prior to 150.0.7871.47 allowed a local attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: Medium)

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

Insufficient validation of untrusted input in the WebAppInstalls component of Google Chrome on Android prior to version 150.0.7871.47 allows a local attacker to potentially escape the sandbox by crafting a malicious file that is processed by the browser.

MitigationUpdate Google Chrome on Android to version 150.0.7871.47 or later to remediate this vulnerability.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Chrome is running on Android
    Check the device operating system. This vulnerability only affects Google Chrome on Android, not iOS or other platforms. Go to Settings > About Phone > Android version to confirm Android OS, and check Chrome app info to confirm Chrome browser.
    Affected if The device is running Android with Google Chrome installed
  2. Locate the Chrome version on Android
    Open Chrome on the Android device, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed at the top of the screen.
    Affected if Unable to determine the Chrome version on the Android device
  3. Compare installed version against the affected range
    Compare the version shown in About Chrome to 150.0.7871.47. Note that version numbers follow a format like X.Y.Z.W where the first number is the major version.
    Affected if The Chrome version on Android is lower than 150.0.7871.47 (for example, 150.0.7871.40 or any version in the 140s, 130s, etc.)
  4. Verify WebAppInstalls component usage
    This vulnerability affects the WebAppInstalls component which handles installation of web apps. Check if any web app installation files (.webapp, manifest.json, or similar) have been processed by Chrome, or review Chrome's download history for any suspicious app installation files.
    Affected if Chrome has processed or is likely to process untrusted web app installation files on this Android device

The user is affected if they are running Google Chrome on Android with a version lower than 150.0.7871.47 and the WebAppInstalls component can process files.

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 on Android to version 150.0.7871.47 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 150.0.7871.47 (Android)

  1. Open Google Chrome on your Android device
  2. Tap the three-dot menu in the top-right corner
  3. Scroll down and tap Settings
  4. Tap About Chrome (or Help and feedback > About Chrome)
  5. If an update is available, tap Update to install version 150.0.7871.47 or later
  6. Restart Chrome if prompted
  7. Verify the version by returning to About Chrome and confirming the version number is 150.0.7871.47 or higher
Caveat Minimal; browser updates typically preserve settings, but clear browser cache if experiencing issues after upgrade

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