CVE-2025-59346

Dragonfly vulnerable to server-side request forgery

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].

There are multiple server-side request forgery (SSRF) vulnerabilities in the DragonFly2 system. The vulnerabilities enable users to force DragonFly2’s components to make requests to internal services, which otherwise are not accessible to the users.
One SSRF attack vector is exposed by the Manager’s API. The API allows users to create jobs. When creating a Preheat type of a job, users provide a URL that the Manager connects to (see figures 2.1–2.3). The URL is weakly validated, and so users can trick the Manager into sending HTTP requests to services that are in the Manager’s local network.

func (p *preheat) CreatePreheat(ctx context.Context, schedulers []models.Scheduler,
json types.PreheatArgs) (*internaljob.GroupJobState, error) {
[skipped]
       url := json.URL
[skipped]
       // Generate download files
       var files []internaljob.PreheatRequest
       switch PreheatType(json.Type) {
       case PreheatImageType:
             // Parse image manifest url
skipped, err := parseAccessURL(url) [skipped]
[skipped]
case PreheatFileType: [skipped]
}

A second attack vector is in peer-to-peer communication. A peer can ask another peer to make a request to an arbitrary URL by triggering the pieceManager.DownloadSource method (figure 2.4), which calls the httpSourceClient.GetMetadata method, which performs the request.

Another attack vector is due to the fact that HTTP clients used by the DragonFly2’s components do not disable support for HTTP redirects. This configuration means that an HTTP request sent to a malicious server may be redirected by the server to a component’s internal service.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Kodem intelligence

Already deployed Kodem?

• Dragonfy v2.1.0 and above.

1. What is CVE-2025-59346? CVE-2025-59346 is a high-severity server-side request forgery (SSRF) vulnerability in github.com/dragonflyoss/dragonfly (go), affecting versions < 2.1.0. It is fixed in 2.1.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. Which packages are affected by CVE-2025-59346?
   • github.com/dragonflyoss/dragonfly (go) (versions < 2.1.0)
   • d7y.io/dragonfly/v2 (go) (versions < 2.1.0)
3. Is there a fix for CVE-2025-59346? Yes. CVE-2025-59346 is fixed in 2.1.0. Upgrade to this version or later.
4. Is CVE-2025-59346 exploitable, and should I be worried? Whether CVE-2025-59346 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
5. What actually determines whether CVE-2025-59346 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.
6. How do I fix CVE-2025-59346?
   • Upgrade github.com/dragonflyoss/dragonfly to 2.1.0 or later
   • Upgrade d7y.io/dragonfly/v2 to 2.1.0 or later

Other vulnerabilities in github.com/dragonflyoss/dragonfly