ChromeWeb browser · Google

CVE-2026-9987

HIGH · 7.8 CVSS v3.1 Published 2026-05-28

Fix available

A fix is available. Upgrade to 148.0.7778.216 or later.

See remediation →

81/100

Remediation priority · High

No privileges

Official description

NVD · unedited

Insufficient validation of untrusted input in WebAppInstalls in Google Chrome on Android prior to 148.0.7778.216 allowed a local attacker to execute arbitrary code via a malicious file. (Chromium security severity: High)

Technical summary

dbcve analysis · high confidence

Insufficient validation of untrusted input in WebAppInstalls in Google Chrome on Android prior to 148.0.7778.216 allows a local attacker to execute arbitrary code via a malicious file. This is a file parsing/validation vulnerability in the web app installation functionality of the Chrome browser on Android devices.

MitigationUpdate Google Chrome for Android to version 148.0.7778.216 or later. Organizations should ensure automatic updates are enabled or push the update to managed devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 148.0.7778.216

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Identify Chrome for Android installation

Open Settings > Apps on the Android device and look for Google Chrome in the app list, or check the Chrome app version via chrome://version

Affected if Google Chrome for Android is not present on the device
Determine the installed Chrome version

In Chrome, navigate to chrome://version or go to Settings > Apps > Google Chrome > App info to view the version number

Affected if The displayed version is lower than 148.0.7778.216
Verify WebAppInstalls component is accessible

Check if the device allows installation of web apps through Chrome - this is typically found in Chrome settings under 'Add to Home screen' or 'Install Web App' features

Affected if WebAppInstalls feature is available and the Chrome version is below 148.0.7778.216
Confirm Android version compatibility

Check the Android OS version in Settings > About Phone > Android version - the vulnerability requires a device capable of running the affected Chrome versions

Affected if Device runs Android and has Chrome installed with version below 148.0.7778.216

A user is affected if Google Chrome for Android is installed with a version number lower than 148.0.7778.216 and the WebAppInstalls feature is accessible on the device.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 148.0.7778.216 or later

Fixed in 148.0.7778.216

Interim mitigation

Update Google Chrome for Android to version 148.0.7778.216 or later. Organizations should ensure automatic updates are enabled or push the update to managed devices.

Recommended fix High confidence

Chrome for Android version 148.0.7778.216 or later

1. Open the Google Play Store app on the Android device
2. Search for "Google Chrome" or locate it in your installed apps
3. Tap "Update" to install the latest version of Chrome
4. Alternatively, enable auto-updates for Chrome in the Play Store settings to ensure future security patches are applied automatically
5. After updating, verify the Chrome version is 148.0.7778.216 or later by navigating to chrome://version

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
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

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,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

chromereleases.googleblog.comVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9987 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-9987?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 148.0.7778.216 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.1%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-9987 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References