CVE-2026-87600: Google Chrome · Improper Input Validation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 153.0.8010.36 when convenient.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-10.
- Patch
- Available – fixed in 153.0.8010.36
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Google Chrome to 153.0.8010.36.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Users should update Google Chrome on Android to version 153.0.8010.36 or later, where this vulnerability is fixed. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-87600 is a medium severity vulnerability in Google Chrome on Android prior to version 153.0.8010.36. It involves improper input validation in the Safebrowsing component, which could allow a remote attacker to bypass system access restrictions by tricking a user into visiting a crafted HTML page. The issue has been fixed in Chrome version 153.0.8010.36.