# CVE-2026-54637: Dragonfly scheduler v1 gRPC unauthenticated SSRF via attacker-controlled PeerHost in DownloadTinyFile

> Remote attackers can exploit unauthenticated gRPC endpoints to perform Server-Side Request Forgery, probing internal services and retrieving limited response data.

- **Severity:** Medium 5.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** CVE-2026-54709, GHSA-chwm-m7g7-685g, GO-2026-5910

## What is CVE-2026-54637?

CVE-2026-54637 is a medium-severity server-side request forgery vulnerability in dragonflyoss dragonfly, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-54637?

3 open source packages ship an affected version, including d7y.io/dragonfly/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `d7y.io/dragonfly/v2` | Go | All versions | 2.4.4-rc.3 |
| `d7y.io/dragonfly/v2` | Go | All versions | 2.4.4-rc.3 |
| `d7y.io/dragonfly/v2` | Go | All versions | 2.4.4-rc.3 |

## How do I fix CVE-2026-54637?

Upgrade d7y.io/dragonfly/v2 to 2.4.4-rc.3 or later.

## Is CVE-2026-54637 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54637 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54637 and fix it if it is affected.

What it is: CVE-2026-54637 is a medium-severity server-side request forgery vulnerability in dragonflyoss dragonfly, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54637 exists.

Affected packages and fixed versions:
- d7y.io/dragonfly/v2 (Go): affected all versions; fixed in 2.4.4-rc.3
- d7y.io/dragonfly/v2 (Go): affected all versions; fixed in 2.4.4-rc.3
- d7y.io/dragonfly/v2 (Go): affected all versions; fixed in 2.4.4-rc.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54637/ (Markdown: https://insights.sbomify.com/CVE-2026-54637/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54637
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54637
- OSV: https://osv.dev/vulnerability/CVE-2026-54637

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54637/
Summaries are generated and may contain mistakes; the official description above is the record.