Skip to content

← Actionable
Low, CVSS 2.0

Dragonfly's directories created via os.MkdirAll are not checked for permissions

CVE-2025-59349GHSA-8425-8r2f-mrv6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/dragonflyoss/dragonfly 2.1.0; d7y.io/dragonfly/v2 2.1.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.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 · score source
EPSS
  • CVE-2025-59349: 0.12% estimated exploitation activity in the next 30 days; percentile 1.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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. Eve has unprivileged access to the machine where Alice uses DragonFly2. Eve watches the commands executed by Alice and introduces new directories/paths with 0777 permissions before DragonFly2 does so. Eve can then delete and forge files in that directory to change the results of further commands executed by Alice. Patches - Dragonfy v2.1.0 and above. Workarounds There are no effective workarounds, beyond upgrading. References A third party security audit was performed by Trail of Bits, you can see the full report. If you have any questions or comments about this advisory, please email…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8425-8r2f-mrv6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59349

Advisory: Dragonfly's directories created via os.MkdirAll are not checked for permissions
IDs: CVE-2025-59349, GHSA-8425-8r2f-mrv6
Record: https://patchnext.com/advisories/cve-2025-59349 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/dragonflyoss/dragonfly 2.1.0; d7y.io/dragonfly/v2 2.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dragonflyoss/dragonfly: affected < 2.1.0; fixed in 2.1.0
- Go d7y.io/dragonfly/v2: affected < 2.1.0; fixed in 2.1.0

## Suggested inspection (read-only)
- Go github.com/dragonflyoss/dragonfly: check the installed version with your package manager.
- Go d7y.io/dragonfly/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dragonflyoss/dragonfly, d7y.io/dragonfly/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8425-8r2f-mrv6 (GitHub-reviewed advisory GHSA-8425-8r2f-mrv6 lists affected ranges: Go github.com/dragonflyoss/dragonfly >=0 =0 <2.1.0)

Commands are suggestions: review each one before running it.

Loading voting…