Skip to main content
CVE-2025-59347VulnerabilityPublished

CVE-2025-59347: dragonflyoss dragonfly · Improper Certificate Validation

Affects dragonflyoss dragonflySource CVE Database V5

0

Not known to be exploited · CVSS 2.7 Low : upgrade to 2.1.0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% 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:L/VA:N/SC:N/SI:L/SA:L/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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

The primary mitigation is to upgrade Dragonfly to version 2.1.0 or later, where proper TLS certificate validation is enforced by default. Organizations should audit their deployments to identify any instances running vulnerable versions and prioritize patching. In environments where immediate upgrading is not feasible, network-level mitigations such as deploying TLS interception detection tools, strict network segmentation, and monitoring for unusual traffic patterns can help detect or reduce the risk of MitM attacks. Additionally, organizations should implement integrity verification mechanisms for files distributed via Dragonfly, such as cryptographic hashes or signatures, to detect tampering regardless of transport security. Enforcing strict access controls and monitoring the Manager component's logs for anomalies can also aid in early detection of exploitation attempts. Finally, educating network and security teams about the risks of disabled certificate validation and the importance of secure TLS configurations can prevent similar issues in other systems.

Description

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, The Manager disables TLS certificate verification in HTTP clients. The clients are not configurable, so users have no way to re-enable the verification. A Manager processes dozens of preheat jobs. An adversary performs a network-level Man-in-the-Middle attack, providing invalid data to the Manager. The Manager preheats with the wrong data, which later causes a denial of service and file integrity problems. This vulnerability is fixed in 2.1.0.

References

Community reviews

Loading reviews…