CVE-2026-10014: Use after free in WebMIDI in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who ha

Routine

HIGH 8.3DOWNGRADE

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

Use after free in WebMIDI in Google Chrome on Android prior to 148.0.7778.216 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)

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-05-28
Last modified	2026-07-21

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-05-28 23:16 UTCPublished CVE record published
2026-07-21 10:10 UTCUpdated Record last modified

google chrome DOWNGRADE

Affected: 148.0.7778.216

Fixed in: no fixed release known

Safe to downgrade to: a release before 148.0.7778.216

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 148.0.7778.216 (Debian / Ubuntu)

apt-cache madison chrome sudo apt install chrome=<VERSION_BEFORE_148.0.7778.216> sudo apt-mark hold chrome

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list chrome sudo dnf downgrade chrome-<VERSION_BEFORE_148.0.7778.216> sudo dnf versionlock add chrome

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-10014?

chrome: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-10014 being exploited?

CVE-2026-10014 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-10014 affect?

CVE-2026-10014 affects chrome. Severity is high (CVSS 8.3). Use after free in WebMIDI in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: H

How urgent is CVE-2026-10014?

Priority 31/100. High severity

Software pages

Android vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-0628 HIGH 8.8 UPGRADE Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker wh
CVE-2026-5285 HIGH 8.8 UPGRADE Use after free in WebGL in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrar
CVE-2026-6315 HIGH 8.8 UPGRADE Use after free in Permissions in Google Chrome on Android prior to 147.0.7727.101 allowed a remote attacker wh
CVE-2026-6363 HIGH 8.8 UPGRADE Type Confusion in V8 in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to potentially perform
CVE-2026-6311 HIGH 8.3 UPGRADE Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attack

References

← Back to latest CVEs