CVE-2025-59353: DragonFly's manager generates mTLS certificates for arbitrary IP addresses
Impact A peer can obtain a valid TLS certificate for arbitrary IP addresses, effectively rendering the mTLS authentication useless. The issue is that the Manager’s Certificate gRPC service does not validate if the requested IP addresses “belong to” the peer requesting the certificate—that is, if the peer connects from the same IP address as the one provided in the certificate request.
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
A peer can obtain a valid TLS certificate for arbitrary IP addresses, effectively rendering the mTLS authentication useless. The issue is that the Manager’s Certificate gRPC service does not validate if the requested IP addresses “belong to” the peer requesting the certificate—that is, if the peer connects from the same IP address as the one provided in the certificate request.
if addr, ok := p.Addr.(*net.TCPAddr); ok {
ip = addr.IP.String()
} else {
ip, _, err = net.SplitHostPort(p.Addr.String())
if err != nil {
return nil, err
}
}
// Parse csr.
[skipped]
// Check csr signature.
// TODO check csr common name and so on.
if err = csr.CheckSignature(); err != nil {
return nil, err
}
[skipped]
// TODO only valid for peer ip
// BTW we need support both of ipv4 and ipv6.
ips := csr.IPAddresses
if len(ips) == 0 {
// Add default connected ip.
ips = []net.IP{net.ParseIP(ip)}
}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-255v-qv84-29p5
- https://github.com/dragonflyoss/dragonfly/blob/main/docs/security/dragonfly-comprehensive-report-2023.pdf
- https://nvd.nist.gov/vuln/detail/CVE-2025-59353
- https://pkg.go.dev/vuln/GO-2025-3969
- https://github.com/advisories/GHSA-255v-qv84-29p5
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
