Summary
Dragonfly's manager makes requests to external endpoints with disabled TLS authentication
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].
Impact
The Manager disables TLS certificate verification in two HTTP clients (figures 3.1 and 3.2). The clients are not configurable, so users have no way to re-enable the verification.
func getAuthToken(ctx context.Context, header http.Header) (string, error) { [skipped]
client := &http.Client{
Timeout: defaultHTTPRequesttimeout,
Transport: &http.Transport{
TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
},
}
[skipped]
}
A Manager processes dozens of preheat jobs. An adversary performs a network-level Man-in-the-Middle attack, providing invalid data to the Manager. The Manager preheats with the wrong data, which later causes a denial of service and file integrity problems.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Dragonfy v2.1.0 and above.
Frequently Asked Questions
- What is CVE-2025-59347? CVE-2025-59347 is a medium-severity improper authentication vulnerability in github.com/dragonflyoss/dragonfly (go), affecting versions < 2.1.0. It is fixed in 2.1.0. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which packages are affected by CVE-2025-59347?
github.com/dragonflyoss/dragonfly(go) (versions < 2.1.0)d7y.io/dragonfly/v2(go) (versions < 2.1.0)
- Is there a fix for CVE-2025-59347? Yes. CVE-2025-59347 is fixed in 2.1.0. Upgrade to this version or later.
- Is CVE-2025-59347 exploitable, and should I be worried? Whether CVE-2025-59347 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-59347 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-59347?
- Upgrade
github.com/dragonflyoss/dragonflyto 2.1.0 or later - Upgrade
d7y.io/dragonfly/v2to 2.1.0 or later
- Upgrade