dbcve.org
DragonflyApplication · Linuxfoundation

CVE-2025-59352

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-17
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, the gRPC API and HTTP APIs allow peers to send requests that force the recipient peer to create files in arbitrary file system locations, and to read arbitrary files. This allows peers to steal other peers’ secret data and to gain remote code execution (RCE) capabilities on the peer’s machine.This vulnerability is fixed in 2.1.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dragonfly P2P file distribution system versions prior to 2.1.0 contain a path traversal vulnerability in both gRPC and HTTP APIs that allows malicious peers to force victim peers to write files to arbitrary filesystem locations and read arbitrary files from the host. This enables complete compromise of peer machines through arbitrary file creation (RCE) and exfiltration of sensitive data.

MitigationUpgrade to Dragonfly version 2.1.0 or later. Additionally, implement strict input validation on file path parameters in API handlers and enforce peer authentication/authorization to prevent untrusted peers from triggering file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DragonflyApplication
Affected:< 2.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dragonfly installation
    Locate the Dragonfly binary or service on the system using package managers, file system searches (e.g., find / -name '*dragonfly*'), or process enumeration tools to confirm Dragonfly is present.
    Affected if Dragonfly is installed and running on the system.
  2. Determine installed Dragonfly version
    Run the version command for Dragonfly (commonly: dragonfly --version, dfget --version, or check the binary version metadata). Compare the version number to the affected range of versions prior to 2.1.0.
    Affected if The installed version is lower than 2.1.0.
  3. Verify if gRPC API is exposed
    Examine Dragonfly configuration files (typically in /etc/dragonfly/ or similar config directories) for gRPC service settings. Check if the gRPC API port is listening and accessible from the network.
    Affected if gRPC API is enabled and accessible to untrusted peers.
  4. Verify if HTTP API is exposed
    Inspect Dragonfly configuration for HTTP API settings (dfdaemon, dfstore, or similar components). Determine if HTTP endpoints are bound to network interfaces accessible from external peers.
    Affected if HTTP API is enabled and accessible to untrusted peers.
  5. Check peer authentication configuration
    Review Dragonfly configuration for peer authentication and authorization settings. Verify whether authentication is required for peer-to-peer connections and file operations.
    Affected if Peer authentication is disabled or permissive, allowing untrusted peers to trigger file operations.

The environment is affected if Dragonfly version is below 2.1.0 and either the gRPC or HTTP API is exposed to untrusted peers without proper authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.0 or later
Fixed in 2.1.0
Vendor patch github.com →
Interim mitigation

Upgrade to Dragonfly version 2.1.0 or later. Additionally, implement strict input validation on file path parameters in API handlers and enforce peer authentication/authorization to prevent untrusted peers from triggering file operations.

Recommended fix High confidence

2.1.0

  1. Back up the current Dragonfly installation and configuration files
  2. Stop the Dragonfly service
  3. Download Dragonfly version 2.1.0 from the official GitHub releases or package repository
  4. Replace the existing Dragonfly binaries with the new version 2.1.0
  5. Restore the backed-up configuration files if needed
  6. Start the Dragonfly service
  7. Verify the service is running correctly and check logs for any errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dragonfly Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59352 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data