CVE-2025-59350: GO-2025-3972 - Dragonfly vulnerable to timing attacks against Proxy’s basic authentication in d7y.io/dragonfly

CVE-2025-59350 · Severity: medium · CVSS 4 · Published 2025-09-24

Dragonfly vulnerable to timing attacks against Proxy’s basic authentication in d7y.io/dragonfly

Technologies: d7y.io/dragonfly/v2 (Go), github.com/dragonflyoss/dragonfly (Go). Vendors: Go.

Quick answers

Is CVE-2025-59350 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-59350 being exploited in the wild.
How severe is CVE-2025-59350?
Medium severity, with a CVSS score of 4, published 24 September 2025.
Which products and versions are affected?
d7y.io/dragonfly/v2 (Go) SEMVER:introduced=0,fixed=2.1.0; github.com/dragonflyoss/dragonfly (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.1.0.
Is there a fix for CVE-2025-59350?
Yes. d7y.io/dragonfly/v2 (Go): upgrade to 2.1.0 or later; github.com/dragonflyoss/dragonfly (Go): upgrade to 2.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-59350?
Check whether you run d7y.io/dragonfly/v2 (Go) or github.com/dragonflyoss/dragonfly (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • d7y.io/dragonfly/v2 (Go): upgrade to 2.1.0 or later
    go get d7y.io/dragonfly/v2@v2.1.0
  • github.com/dragonflyoss/dragonfly (Go): upgrade to 2.1.0 or later
    go get github.com/dragonflyoss/dragonfly@v2.1.0

Affected products

  • d7y.io/dragonfly/v2 (Go) SEMVER:introduced=0,fixed=2.1.0
  • github.com/dragonflyoss/dragonfly (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.1.0

Identifiers

  • CVE-2025-59350
  • GHSA-c2fc-9q9c-5486
  • GO-2025-3972

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.