Skip to main content
CVE-2025-59353VulnerabilityPublished

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

Affects dragonflyoss dragonflySource CVE Database V5

0

Not known to be exploited · CVSS 7.7 High : upgrade to 2.1.0 soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% 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:H/VA:N/SC:N/SI:N/SA:N/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: 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 all Dragonfly instances to version 2.1.0 or later, where the certificate validation flaw has been corrected. Organizations should audit their environments to identify any deployments running vulnerable versions and prioritize patching. In addition, network segmentation and strict access controls should be enforced to limit peer communication to trusted IP ranges and authenticated entities. Implementing additional monitoring on the Manager’s Certificate gRPC service for anomalous certificate requests or unexpected IP address bindings can help detect exploitation attempts. Where feasible, organizations should consider deploying network-level TLS inspection and anomaly detection tools to identify suspicious mTLS traffic patterns. Finally, integrating Dragonfly usage into broader supply chain security and vulnerability management programs will help ensure timely detection and remediation of similar issues in the future.

Description

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, a peer can obtain a valid TLS certificate for arbitrary IP addresses, effectively rendering the mTLS authentication useless. The issue is that the Manager’s Certificate gRPC service does not validate if the requested IP addresses “belong to” the peer requesting the certificate—that is, if the peer connects from the same IP address as the one provided in the certificate request. This vulnerability is fixed in 2.1.0.

References

Community reviews

Loading reviews…