Site isolation issue in the Networking component. This vulnerability was fixed in Firefox 153, Firefox ESR 140.13, Thunderbird 153, and Thunderbird 140.13.
CVE-2026-16387
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 24, 2026
Advisory Details (5)
Auto-updated Jul 25, 2026Security Vulnerabilities fixed in Thunderbird 140.13 — Mozilla
https://www.mozilla.org/security/advisories/mfsa2026-72/Security Vulnerabilities fixed in Thunderbird 153 — Mozilla
https://www.mozilla.org/security/advisories/mfsa2026-71/Security Vulnerabilities fixed in Firefox ESR 140.13 — Mozilla
https://www.mozilla.org/security/advisories/mfsa2026-70/Security Vulnerabilities fixed in Firefox 153 — Mozilla
https://www.mozilla.org/security/advisories/mfsa2026-68/Vendor Advisories for CVE-2026-16387(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 33× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 06:22 UTCGHSA enrichment
- 2026-07-28 02:01 UTCGHSA enrichment
- 2026-07-27 21:41 UTCGHSA enrichment
- 2026-07-27 17:06 UTCEG score recompute
- 2026-07-27 17:05 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:45 UTCGHSA enrichment
- 2026-07-27 08:25 UTCGHSA enrichment
- 2026-07-27 04:04 UTCGHSA enrichment
- 2026-07-26 23:41 UTCGHSA enrichment
- 2026-07-26 19:21 UTCGHSA enrichment
- 2026-07-26 15:01 UTCEG score recompute
- 2026-07-26 15:01 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:42 UTCEG score recompute
- 2026-07-26 10:42 UTCGHSA enrichment
- 2026-07-26 04:22 UTCEG score recompute
- 2026-07-26 04:22 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:13 UTCEG score recompute
Show 8 moreShow fewer
- 2026-07-22 23:13 UTCGHSA enrichment
- 2026-07-22 17:37 UTCEG score recompute▲ 9.80
- 2026-07-22 17:36 UTCGHSA enrichment
- 2026-07-22 17:35 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 14:51 UTCNVD update
- 2026-07-21 12:48 UTCEG score recompute
- 2026-07-21 12:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-16387?
When was CVE-2026-16387 disclosed?
Is CVE-2026-16387 actively exploited?
What is the CVSS score of CVE-2026-16387?
How do I remediate CVE-2026-16387?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16387
Is Your Infrastructure Affected by CVE-2026-16387?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.