Skip to main content
VulnerabilityPublished

CVE-2025-59349: dragonflyoss dragonfly · Incorrect Permissions

Affects dragonflyoss dragonflySource CVE Database V5

0

Public exploit available · CVSS 2.0 Low : upgrade to 2.1.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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: 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

European organizations should upgrade Dragonfly to version 2.1.0 or later, where this vulnerability is fixed. Until upgrading is possible, organizations should implement strict local access controls to limit who can create or modify directories used by Dragonfly. File system monitoring and integrity checking tools can be deployed to detect unauthorized changes to directories and files managed by Dragonfly. Additionally, running Dragonfly processes with the least privilege necessary and isolating them in containers or sandboxed environments can reduce the risk of local tampering. Administrators should audit existing directory permissions to ensure no overly permissive directories exist that could be exploited. Incorporating automated deployment pipelines with cryptographic verification of distributed files can help detect tampering resulting from this vulnerability. Finally, organizations should educate local users about the risks of unauthorized directory creation and monitor logs for suspicious local activity related to Dragonfly directories.

Description

Dragonfly is an open source P2P-based file distribution and image acceleration system. Prior to 2.1.0, DragonFly2 uses the os.MkdirAll function to create certain directory paths with specific access permissions. This function does not perform any permission checks when a given directory path already exists. This allows a local attacker to create a directory to be used later by DragonFly2 with broad permissions before DragonFly2 does so, potentially allowing the attacker to tamper with the files. This vulnerability is fixed in 2.1.0.

References

Community reviews

Loading reviews…