What is CVE-2026-87518?
Observable discrepancy in Safebrowsing in Google Chrome on on iOS prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to potentially obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
The record classifies CVE-2026-87518 under weakness class CWE-203. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 32 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 5.3 — MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 19.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-09
Is CVE-2026-87518 being exploited?
It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.
Affected products and versions
- Google: Chrome
How to fix CVE-2026-87518
No vendor patch reference has been recorded for CVE-2026-87518 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-87518
1 tracked threat in the Threadlinqs corpus references CVE-2026-87518, either in the campaign’s CVE list or as an indicator on the campaign record.
- Multiple Vulnerabilities in Microsoft Edge prior to 154.0.4258.53 (HK GovCERT A26-10-03) — CRITICAL · 2026-10-02
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .