Dalfox Server Mode has an Unauthenticated Arbitrary File Create/Append via output Option

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-45089: 0.24% estimated exploitation activity in the next 30 days; percentile 15.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When dalfox is run in REST API server mode, the output, output-all, and debug fields in model.Options are JSON-tagged and deserialized directly from the attacker's request body, then propagated unchanged through dalfox.Initialize into the scan engine's logging path. The logger opens the attacker-supplied path with os.OAPPEND|os.OCREATE|os.OWRONLY and writes scan log lines to it. Critically, this file write block lives outside the IsLibrary guard in DalLog, so it executes even in server/library mode where file output was never intended to operate. Because no API key is required in the default configuration, an unauthenticated network caller can create or append to any file writable by the dalfox process on the host filesystem. Severity High (CVSS 3.1: 8.2) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L - Attack Vector: Network — server binds to 0.0.0.0:6664 by default. - Attack Complexity: Low — no preconditions; all trigger options (output, output-all, debug) are fully…

Published by the source

12 May 2026, 15:08 UTC

Last modified by the source

8 Jun 2026, 23:50 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8hf9-3q64-q2qf

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

# Patch Next advisory brief: CVE-2026-45089

Advisory: Dalfox Server Mode has an Unauthenticated Arbitrary File Create/Append via `output` Option
IDs: CVE-2026-45089, GHSA-8hf9-3q64-q2qf
Record: https://patchnext.com/advisories/cve-2026-45089 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/hahwul/dalfox/v2 2.13.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/hahwul/dalfox/v2: affected <= 2.12.0; fixed in 2.13.0

## Suggested inspection (read-only)
- Go github.com/hahwul/dalfox/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/hahwul/dalfox/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-8hf9-3q64-q2qf (GitHub-reviewed advisory GHSA-8hf9-3q64-q2qf lists affected ranges: Go github.com/hahwul/dalfox/v2 >=0 <=2.12.0)

Commands are suggestions: review each one before running it.