Skip to main content
VulnerabilityPublished

CVE-2025-59352: dragonflyoss dragonfly · Exposure of Sensitive Information Through Data Queries

Affects dragonflyoss dragonflySource CVE Database V5

0

Public exploit available · CVSS 6.9 Medium : upgrade to 2.1.0 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade dragonflyoss dragonfly to 2.1.0.

Affected software

ProductAffectedFixed in
dragonflyoss dragonflyAffected
  • <2.1.0
Fixed in
  • 2.1.0

AI-suggested

Organizations should upgrade all Dragonfly deployments to version 2.1.0 or later immediately to remediate this vulnerability. Until upgrades are feasible, restrict network access to Dragonfly peers to trusted entities only, using network segmentation and firewall rules to limit exposure. Implement strict monitoring and logging of API requests to detect anomalous file creation or access patterns indicative of exploitation attempts. Employ host-based intrusion detection systems (HIDS) to identify unauthorized file system changes. Review and harden file system permissions on nodes running Dragonfly to minimize damage from arbitrary file writes. Consider deploying application-layer gateways or API proxies that validate and sanitize incoming requests to Dragonfly APIs. Finally, conduct thorough security assessments of the Dragonfly deployment architecture to ensure no unnecessary exposure of peers to untrusted networks.

Description

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.

References

Community reviews

Loading reviews…