CVE-2026-54637

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-78576 (ENISA EUVD) · GHSA-chwm-m7g7-685g (GitHub Security Advisories) · GO-2026-5910 (OSV.dev)Source: ENISA EUVD

5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.4.4-rc.3, the scheduler's default unauthenticated v1 gRPC flow accepts attacker-controlled PeerHost.Ip and PeerHost.DownPort values through RegisterPeerTask and ReportPeerResult, storeHost copies those values into resource.Host, and handlePeerSuccess invokes Peer.DownloadTinyFile() for a TINY task. DownloadTinyFile() in scheduler/resource/standard/peer.go builds an HTTP GET request from the supplied address without destination validation, allowing a remote attacker to probe loopback, link-local, and private services and place up to TinyFileSize, 128 bytes, of a response in Task.DirectPiece for later retrieval. PeerHost.DownPort is restricted to ports 1024 through 65534, and the issue provides read SSRF rather than remote code execution. The remediation blocks loopback and link-local targets, while RFC1918 destinations remain reachable because IsGlobalUnicast accepts private ranges. This issue is fixed in 2.4.4-rc.3.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 6, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v2.4.4-rc.3

Patch available: dragonflyoss/dragonfly v2.4.4-rc.3

https://github.com/dragonflyoss/dragonfly/releases/tag/v2.4.4-rc.3
GitHub commit

commit 4f9bd93d2245 (dragonflyoss/dragonfly)

Fix landed in dragonflyoss/dragonfly commit 4f9bd93d2245 — awaiting tagged release

https://github.com/dragonflyoss/dragonfly/commit/4f9bd93d22453e3f433f9d912bfeeca22760c237
GitHub advisoryMentions a patch (unverified)

Dragonfly scheduler v1 gRPC unauthenticated SSRF via attacker-controlled PeerHost in DownloadTinyFile · Advisory · dragonflyoss/dragonfly · GitHub

https://github.com/dragonflyoss/dragonfly/security/advisories/GHSA-chwm-m7g7-685g

Vendor Advisories for CVE-2026-54637(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
god7y.io/dragonfly/v2 @ 2.4.4-rc.3 (fixes <= 2.4.4-rc.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
d7y.io/dragonfly/v2—
  • every version up to 2.4.4-rc.3: fixed in 2.4.4-rc.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  3. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-chwm-m7g7-685g · GitHub severity MODERATE
  4. 2026-11-01 07:44 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-30 11:25 UTCOSV refresh
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-10-25 14:19 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  16. 2026-10-22 21:20 UTCEG score recompute
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-10-18 03:30 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
Show 42 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:39 UTCEG score recompute
  6. 2026-10-11 16:54 UTCEG score recompute
  7. 2026-10-11 14:17 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-09-30 18:11 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-09-28 13:42 UTCEG score recompute
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  26. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  27. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-23 06:22 UTCEG score recompute
  29. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-18 05:59 UTCEG score recompute
  32. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-16 19:26 UTCEG score recompute
  34. 2026-09-16 18:27 UTCEG score recompute
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-15 15:35 UTCEG score recompute
  37. 2026-09-15 14:18 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
  38. 2026-09-15 14:18 UTCMITRE cvelistV5CVSS v3 → 5.5 · CVSS v4 → 5.5
  39. 2026-07-31 23:14 UTCEG score recompute
  40. 2026-07-26 12:46 UTCEG score recompute
  41. 2026-07-23 03:19 UTCEG score recompute
  42. 2026-07-06 20:37 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54637?
CVE-2026-54637 is a medium-severity vulnerability; its CVE record was published on July 6, 2026. Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.4.4-rc.3, the scheduler's default unauthenticated v1 gRPC flow accepts attacker-controlled PeerHost.Ip and PeerHost.DownPort values through RegisterPeerTask and ReportPeerResult, storeHost copies those…
When was the CVE record for CVE-2026-54637 published?
The CVE record for CVE-2026-54637 was published on July 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54637 actively exploited?
CVE-2026-54637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54637?
CVE-2026-54637 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54637?
A fix for CVE-2026-54637 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54637 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54637

Explore →

Is Your Infrastructure Affected by CVE-2026-54637?

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