CVE-2025-59354VulnerabilityPublished 17 Sep 2025

CVE-2025-59354: dragonflyoss dragonfly · Use of Weak Hash

Affects dragonflyoss dragonflySource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.1.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% 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:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade dragonflyoss dragonfly to 2.1.0.

Affected software

Product	Affected	Fixed in
dragonflyoss dragonfly	Affected <2.1.0	Fixed in 2.1.0

AI-suggested

1. Immediate upgrade to Dragonfly version 2.1.0 or later, which replaces weak hash functions with secure alternatives, is the primary mitigation step. 2. For organizations unable to upgrade immediately, implement network-level controls to restrict access to Dragonfly services only to trusted internal networks to reduce exposure. 3. Employ additional integrity verification mechanisms outside of Dragonfly’s native hashing, such as digital signatures or SHA-256 based checksums, to validate downloaded files. 4. Monitor network traffic and logs for unusual file replacement activities or unexpected file hashes. 5. Integrate supply chain security best practices, including verifying the provenance of distributed files and using reproducible builds. 6. Conduct security awareness training for developers and DevOps teams about the risks of weak cryptographic primitives and the importance of timely patching. 7. Review and audit existing deployment pipelines to ensure no legacy Dragonfly versions remain in use.

Description

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, the DragonFly2 uses a variety of hash functions, including the MD5 hash, for downloaded files. This allows attackers to replace files with malicious ones that have a colliding hash. This vulnerability is fixed in 2.1.0.

Impact

For European organizations using Dragonfly versions prior to 2.1.0, this vulnerability poses a risk of supply chain compromise through file tampering. Attackers could inject malicious payloads into distributed files, potentially leading to malware infections, unauthorized code execution, or data corruption. This could affect organizations relying on Dragonfly for image acceleration or file distribution in critical infrastructure, software development, or content delivery networks. The integrity compromise could undermine trust in software updates or distributed content, leading to operational disruptions or reputational damage. However, since confidentiality and availability are not directly impacted, the threat is primarily to data integrity. The lack of authentication requirement and remote exploitability increase the risk, especially in environments where Dragonfly is exposed to untrusted networks. European organizations with automated deployment pipelines or containerized environments using Dragonfly are particularly at risk if they have not upgraded to the patched version.

CWE-328Use of Weak Hash (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).
Architecture and Design
Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V8.3.7 (opens in a new tab)
V2.9.3 (opens in a new tab)
Attack patterns
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Subvert Code-signing Facilities (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Sep 2025, 00:39 UTC

WeaknessesCWE-328

Technical details

References

Community reviews

Related threats