Summary
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 access control mechanism for the Proxy feature uses simple string comparisons and is therefore vulnerable to timing attacks. An attacker may try to guess the password one character at a time by sending all possible characters to a vulnerable mechanism and measuring the comparison instruction’s execution times.
The vulnerability is shown in figure 8.1, where both the username and password are compared with a short-circuiting equality operation.
if user != proxy.basicAuth.Username || pass != proxy.basicAuth.Password {
It is currently undetermined what an attacker may be able to do with access to the proxy password.
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.
Remediation advice
- Dragonfy v2.1.0 and above.
Frequently Asked Questions
- What is CVE-2025-59350? CVE-2025-59350 is a medium-severity security vulnerability in github.com/dragonflyoss/dragonfly (go), affecting versions < 2.1.0. It is fixed in 2.1.0.
- Which packages are affected by CVE-2025-59350?
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-59350? Yes. CVE-2025-59350 is fixed in 2.1.0. Upgrade to this version or later.
- Is CVE-2025-59350 exploitable, and should I be worried? Whether CVE-2025-59350 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-59350 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-59350?
- Upgrade
github.com/dragonflyoss/dragonflyto 2.1.0 or later - Upgrade
d7y.io/dragonfly/v2to 2.1.0 or later
- Upgrade