CVE-2026-84894

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

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

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

In moxygen before commit 004123dd24c3, MoQSession::dataStreamReadLoop keeps using a stream read handle after reading a FIN, which invalidates the handle under proxygen's WebTransport API. A remote peer can trigger the stale use by opening a data stream that names an unknown track alias and carries the FIN in the same write.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

CVE-2026-84894

https://www.facebook.com/security/advisories/cve-2026-84894
github_commit

commit 004123dd24c3 (facebookexperimental/moxygen)

Fix landed in facebookexperimental/moxygen commit 004123dd24c3 — awaiting tagged release

https://github.com/facebookexperimental/moxygen/commit/004123dd24c30dad6b649163575145f240dabc94

Vendor Advisories for CVE-2026-84894(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 27× in last 7d / 27× 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-10-05 06:02 UTCEG score recompute
  2. 2026-10-05 06:02 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 18:15 UTCGHSA enrichment
  5. 2026-10-04 06:28 UTCGHSA enrichment
  6. 2026-10-03 18:42 UTCEG score recompute
  7. 2026-10-03 18:42 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 06:55 UTCGHSA enrichment
  10. 2026-10-02 19:08 UTCEG score recompute
  11. 2026-10-02 19:08 UTCGHSA enrichment
  12. 2026-10-02 17:57 UTCEPSS rescore
  13. 2026-10-02 07:22 UTCEG score recompute
  14. 2026-10-02 07:22 UTCGHSA enrichment
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-10-01 19:35 UTCGHSA enrichment
  17. 2026-10-01 07:48 UTCGHSA enrichment
  18. 2026-09-30 20:02 UTCEG score recompute
  19. 2026-09-30 20:02 UTCGHSA enrichment
  20. 2026-09-30 16:26 UTCGHSA enrichment
  21. 2026-09-30 15:29 UTCEG score recompute▲ 7.50
  22. 2026-09-30 15:29 UTCGHSA enrichment
  23. 2026-09-30 15:27 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  24. 2026-09-30 15:04 UTCEPSS rescore
  25. 2026-09-28 19:21 UTCNVD update
Show 2 more
  1. 2026-09-28 18:52 UTCEG score recompute
  2. 2026-09-28 18:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84894?
CVE-2026-84894 is a high vulnerability published on September 28, 2026. In moxygen before commit 004123dd24c3, MoQSession::dataStreamReadLoop keeps using a stream read handle after reading a FIN, which invalidates the handle under proxygen's WebTransport API. A remote peer can trigger the stale use by opening a data stream that names an unknown track alias and carries…
When was CVE-2026-84894 disclosed?
CVE-2026-84894 was first published on September 28, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84894 actively exploited?
CVE-2026-84894 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84894?
CVE-2026-84894 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-84894?
An upstream fix for CVE-2026-84894 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-84894 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-84894?

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

Book a Demo →Browse All CVEs