CVE-2026-13927: Insufficient validation of untrusted input in UI in Google Chrome on Android prior to 150.0.7871.47 allowed a

Q: How do I fix CVE-2026-13927?

chrome: upgrade to 150.0.7871.47. Exact commands for each OS are on this page.

Q: Is CVE-2026-13927 being exploited?

CVE-2026-13927 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-13927 affect?

CVE-2026-13927 affects chrome. Severity is high (CVSS 7.8). Insufficient validation of untrusted input in UI in Google Chrome on Android prior to 150.0.7871.47 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)

Routine

HIGH 7.8UPGRADE

CVE-2026-13927 is a high-severity flaw (CVSS 7.8) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Insufficient validation of untrusted input in UI in Google Chrome on Android prior to 150.0.7871.47 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-20
Published	2026-06-30
Last modified	2026-10-25

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-30 23:17 UTCPublished CVE record published
2026-10-25 21:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 150.0.7871.47

Fixed in: 150.0.7871.47

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 150.0.7871.47 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-13927?

chrome: upgrade to 150.0.7871.47. Exact commands for each OS are on this page.

Is CVE-2026-13927 being exploited?

CVE-2026-13927 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-13927 affect?

CVE-2026-13927 affects chrome. Severity is high (CVSS 7.8). Insufficient validation of untrusted input in UI in Google Chrome on Android prior to 150.0.7871.47 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)

How urgent is CVE-2026-13927?

Priority 28/100. High severity

Software pages

Android vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-6299 HIGH 8.8 UPGRADE Use after free in Prerender in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbi
CVE-2026-6300 HIGH 8.8 UPGRADE Use after free in CSS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary
CVE-2026-6307 HIGH 8.8 UPGRADE Type Confusion in Turbofan in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbit
CVE-2026-8018 HIGH 8.1 UPGRADE Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed a remote attacker
CVE-2026-8016 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrar

References

← Back to latest CVEs