CVE-2026-16370

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Mitigation bypass in the DOM: Networking component. This vulnerability was fixed in Firefox 153 and Thunderbird 153.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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 computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic

Security Vulnerabilities fixed in Firefox 153 — Mozilla

https://www.mozilla.org/security/advisories/mfsa2026-68/
generic

Access Denied

https://bugzilla.mozilla.org/show_bug.cgi?id=1996495

Vendor Advisories for CVE-2026-16370(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× 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.

  1. 2026-07-28 04:12 UTCGHSA enrichment
  2. 2026-07-28 00:30 UTCGHSA enrichment
  3. 2026-07-27 20:49 UTCGHSA enrichment
  4. 2026-07-27 16:44 UTCEG score recompute
  5. 2026-07-27 16:44 UTCGHSA enrichment
  6. 2026-07-27 14:13 UTCEPSS rescore
  7. 2026-07-27 13:02 UTCGHSA enrichment
  8. 2026-07-27 09:20 UTCGHSA enrichment
  9. 2026-07-27 05:39 UTCGHSA enrichment
  10. 2026-07-27 01:48 UTCGHSA enrichment
  11. 2026-07-26 22:07 UTCGHSA enrichment
  12. 2026-07-26 18:26 UTCEG score recompute
  13. 2026-07-26 18:26 UTCGHSA enrichment
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:22 UTCGHSA enrichment
  17. 2026-07-26 10:42 UTCEG score recompute
  18. 2026-07-26 10:42 UTCGHSA enrichment
  19. 2026-07-26 04:22 UTCEG score recompute
  20. 2026-07-26 04:22 UTCGHSA enrichment
  21. 2026-07-25 14:17 UTCEPSS rescore
  22. 2026-07-25 14:17 UTCEPSS rescore
  23. 2026-07-24 14:17 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
Show 10 more
  1. 2026-07-23 03:05 UTCEG score recompute
  2. 2026-07-22 23:16 UTCEG score recompute
  3. 2026-07-22 23:16 UTCGHSA enrichment
  4. 2026-07-22 16:31 UTCEG score recompute▲ 9.10
  5. 2026-07-22 16:31 UTCGHSA enrichment
  6. 2026-07-22 16:30 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 14:51 UTCNVD update
  9. 2026-07-21 12:50 UTCEG score recompute
  10. 2026-07-21 12:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16370?
CVE-2026-16370 is a critical vulnerability published on July 21, 2026. Mitigation bypass in the DOM: Networking component. This vulnerability was fixed in Firefox 153 and Thunderbird 153.
When was CVE-2026-16370 disclosed?
CVE-2026-16370 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16370 actively exploited?
CVE-2026-16370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16370?
CVE-2026-16370 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16370, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16370

Explore →

Is Your Infrastructure Affected by CVE-2026-16370?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs