Cyber Resilience

CVE-2025-59354

Crypto Weakness in Linuxfoundation Dragonfly ≤ 2.1.0

Crypto Weakness
Published
17 September 2025
Modified
18 September 2025
Patch / advisory
View advisory
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0015 5th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-59354 is a medium-severity Use of Weak Hash (CWE-328) vulnerability in Linuxfoundation Dragonfly. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Software Supply Chain (T1195.002); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

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…

more

have a colliding hash. This vulnerability is fixed in 2.1.0.

CWE(s)
CWE-328

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1525 Implant Internal Image Persistence
Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment.
attack.mitre.org →
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Why these techniques?

Weak MD5-based integrity checks in Dragonfly's P2P file and image distribution allow hash collision attacks to substitute malicious files/images for legitimate ones, enabling supply chain compromise, internal image implantation, and undetected transmitted data manipulation.

MITRE ATLAS TechniquesAI

MITRE ATLAS techniques

AML.T0010: AI Supply Chain Compromise

CVEs Like This One

CVE-2025-59347Same product: Linuxfoundation Dragonfly
CVE-2025-59350Same product: Linuxfoundation Dragonfly
CVE-2025-59346Same product: Linuxfoundation Dragonfly
CVE-2026-24124Same product: Linuxfoundation Dragonfly
CVE-2025-59348Same product: Linuxfoundation Dragonfly
CVE-2025-59345Same product: Linuxfoundation Dragonfly
CVE-2025-59353Same product: Linuxfoundation Dragonfly
CVE-2025-59410Same product: Linuxfoundation Dragonfly
CVE-2025-59352Same product: Linuxfoundation Dragonfly
CVE-2023-27584Same product: Linuxfoundation Dragonfly

Affected Assets

linuxfoundation
dragonfly
≤ 2.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-13 Cryptographic Protection
  • SI-7 Software, Firmware, and Information Integrity
  • CM-14 Signed Components
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.2.3
  • V6.5.2

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match
prevent

Mandates approved cryptographic mechanisms for integrity protection, directly prohibiting weak collision-prone hashes such as MD5 for file verification.

SI-7 Software, Firmware, and Information Integrity good match
preventdetect

Requires cryptographic integrity checks on software and information, ensuring only collision-resistant hashes are accepted for downloaded files.

CM-14 Signed Components partial match
prevent

Enforces use of signed components, providing a stronger integrity mechanism than raw MD5 hashes and mitigating collision attacks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-SDLC requirements explicitly forbid weak cryptographic algorithms, fully preventing CWE-328 while covering only one aspect of development practice.

PR.DS-01 mostly match
prevents

Proper data-at-rest integrity protection requires strong cryptographic hashes, directly blocking weak-hash usage.

PR.DS-02 mostly match
prevents

Data-in-transit integrity likewise depends on strong hashes, so the control prevents the weakness while the weakness only partially satisfies the outcome.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandates use of approved cryptographic algorithms, directly preventing weak-hash selection.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect weak-hash usage but does not prescribe algorithm choice.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong hashing, but the control is broader.

A.8.28 Secure coding partial match
prevents

Requires secure coding standards that forbid weak hash functions in source code.

References