Dalfox Server Mode Vulnerable to Unauthenticated Remote Code Execution via found-action

Exploitation

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

CVSS

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

EPSS

• CVE-2026-45087: 8.73% estimated exploitation activity in the next 30 days; percentile 95.16 (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.

GHSA: Unauthenticated Remote Code Execution via found-action in Dalfox Server Mode Summary When dalfox is started in REST API server mode (dalfox server), the server binds to 0.0.0.0:6664 by default and requires no API key unless the operator explicitly passes --api-key. Because model.Options — including FoundAction and FoundActionShell — is deserialized directly from attacker-supplied JSON in POST /scan, and because dalfox.Initialize explicitly propagates those two fields into the final scan options without stripping them, any unauthenticated caller who can reach the server port can supply an arbitrary shell command that the dalfox process will execute on the host whenever a scan finding is triggered. Severity Critical (CVSS 3.1: 10.0) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Attack Vector: Network — the server binds to 0.0.0.0 by default; reachable by any network peer. - Attack Complexity: Low — the attacker fully controls the scanned URL and can trivially host a one-line…

Published by the source

12 May 2026, 15:07 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-v25v-m36w-jp4h

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

# Patch Next advisory brief: CVE-2026-45087

Advisory: Dalfox Server Mode Vulnerable to Unauthenticated Remote Code Execution via `found-action`
IDs: CVE-2026-45087, GHSA-v25v-m36w-jp4h
Record: https://patchnext.com/advisories/cve-2026-45087 (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: Critical (CVSS 10.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/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-v25v-m36w-jp4h (GitHub-reviewed advisory GHSA-v25v-m36w-jp4h lists affected ranges: Go github.com/hahwul/dalfox/v2 >=0 <=2.12.0)

Commands are suggestions: review each one before running it.