CVE-2025-59410: DragonFly's tiny file download uses hard coded HTTP protocol
Impact The code in the scheduler for downloading a tiny file is hard coded to use the HTTP protocol, rather than HTTPS. This means that an attacker could perform a Man-in-the-Middle attack, changing the network request so that a different piece of data gets downloaded. Due to the use of weak integrity checks (TOB-DF2-15), this modification of the data may go unnoticed.
Published Sep 17, 2025 · Updated Sep 26, 2025
Affected packages
github.com/dragonflyoss/dragonfly
- Ecosystem
- Go
- Affected
- < 2.1.0
- Fixed in
- 2.1.0
- Check
go list -m github.com/dragonflyoss/dragonfly
d7y.io/dragonfly/v2
- Ecosystem
- Go
- Affected
- < 2.1.0
- Fixed in
- 2.1.0
- Check
go list -m d7y.io/dragonfly/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The code in the scheduler for downloading a tiny file is hard coded to use the HTTP protocol, rather than HTTPS. This means that an attacker could perform a Man-in-the-Middle attack, changing the network request so that a different piece of data gets downloaded. Due to the use of weak integrity checks (TOB-DF2-15), this modification of the data may go unnoticed.
// DownloadTinyFile downloads tiny file from peer without range.
func (p *Peer) DownloadTinyFile() ([]byte, error) {
ctx, cancel := context.WithTimeout(context.Background(),
downloadTinyFileContextTimeout)
defer cancel()
// Download url:
http://${host}:${port}/download/${taskIndex}/${taskID}?peerId=${peerID}
targetURL := url.URL{
Scheme:
}
"http",
fmt.Sprintf("%s:%d", p.Host.IP, p.Host.DownloadPort),
fmt.Sprintf("download/%s/%s", p.Task.ID[:3], p.Task.ID),
Host:
Path:
RawQuery: fmt.Sprintf("peerId=%s", p.ID),A network-level attacker who cannot join a peer-to-peer network performs a Man-in-the-Middle attack on peers. The adversary can do this because peers (partially) communicate over plaintext HTTP protocol. The attack chains this vulnerability with the one described in TOB-DF2-15 to replace correct files with malicious ones. Unconscious peers use the malicious files.
Patches
- Dragonfy v2.1.0 and above.
Workarounds
There are no effective workarounds, beyond upgrading.
References
A third party security audit was performed by Trail of Bits, you can see the full report.
If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected]).
Credited to gaius-qi.
References
- https://github.com/dragonflyoss/dragonfly/security/advisories/GHSA-mcvp-rpgg-9273
- https://github.com/dragonflyoss/dragonfly/blob/main/docs/security/dragonfly-comprehensive-report-2023.pdf
- https://nvd.nist.gov/vuln/detail/CVE-2025-59410
- https://pkg.go.dev/vuln/GO-2025-3974
- https://github.com/advisories/GHSA-mcvp-rpgg-9273
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-54637
Dragonfly scheduler v1 and v2 gRPC unauthenticated SSRF via attacker-controlled PeerHost in DownloadTinyFile
medium5.5Jul 6, 2026CVE-2026-49254
Dragonfly Manager OAuth provider client_secret disclosure via unauthenticated GET /api/v1/oauth
low2.9Jul 2, 2026CVE-2026-24124
Dragonfly Manager Job API Unauthenticated Access
high8.9Jan 22, 2026CVE-2025-59345
Dragonfly doesn't have authentication enabled for some Manager’s endpoints
high7.7Sep 17, 2025CVE-2025-59346
Dragonfly vulnerable to server-side request forgery
high7.7Sep 17, 2025CVE-2025-59347
Dragonfly's manager makes requests to external endpoints with disabled TLS authentication
medium5.5Sep 17, 2025
