CVE-2026-45087: Dalfox: Unauthenticated Remote Code Execution via `found-action` in Dalfox Server Mode
Dalfox is a powerful open-source XSS scanner and utility focused on automation. Prior to 2.13.0, 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. This vulnerability is fixed in 2.13.0.
HarborGuard Analysis
HarborGuard analysisSynopsis
An unauthenticated remote code execution vulnerability exists in Dalfox, the open-source XSS scanning tool, when it is run in REST API server mode. The server binds to all interfaces by default with no authentication required, and attacker-supplied JSON in a POST /scan request can set arbitrary shell commands via the FoundAction and FoundActionShell fields, which are passed directly into scan execution without sanitization. Successful exploitation gives the attacker full command execution on the host running the Dalfox server process. No fix version has been published yet; HarborGuard tracks this advisory and will make a patched-image rebuild available as soon as an upstream fix is released.
HarborGuard Coverage
Detection of CVE-2026-45087 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of publication from upstream advisory feeds, including custom-built images that bundle Dalfox. Coverage applies to both registry scans and images evaluated at pipeline build time.
AvailableTriage is available with the full CVSS v3.1 score of 10.0 (Critical) applied to every matched image, weighted further by each customer's per-environment compliance policy. Findings are routed to the appropriate team inbox within each customer organization based on configured ownership rules.
AvailableBecause no fix version has been published, HarborGuard re-checks this advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment an upstream fix appears. In the meantime, customers with auto-remediation enabled will receive the rebuilt image, a regression-test run, and a PR opened against affected workloads as soon as version 2.13.0 or a later fix version is confirmed upstream.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The attacker must reach the Dalfox server port (default 6664) over the network, as the service binds to 0.0.0.0 and is exposed to any host that can route to it.
- AuthenticationNot required
No API key or credentials are required by default; the server accepts unauthenticated POST requests unless the operator has explicitly passed the --api-key flag at startup.
- Victim interactionNot required
Exploitation is fully automated and requires no action from any user or operator on the target system.
- Attack complexityDetail
The exploit is reliable and condition-free; the attacker simply sends a crafted JSON body to a known endpoint with no race conditions or environmental dependencies to satisfy.
Blast Radius
- The attacker executes arbitrary shell commands as the OS user running the Dalfox server process, gaining full control over that process and its accessible filesystem paths.
- All secrets, credentials, and environment variables visible to the Dalfox process (such as API tokens or cloud credentials injected at container runtime) are readable.
- The attacker can modify or delete files accessible to the process, including scan result data and any mounted volumes.
- The Dalfox service itself can be crashed or hijacked, disrupting any automated scanning pipelines that depend on it.
How HarborGuard Handles This
Available on HarborGuard: detection of CVE-2026-45087 is active for any image containing a Dalfox binary older than a confirmed fix version, with findings surfaced at Critical severity. Because no upstream fix has been published as of the CVE publication date, HarborGuard monitors this advisory on every ingest cycle and will generate a patched-image rebuild automatically once a fix version is confirmed. For customers who opt into auto-remediation, the rebuild, regression-test run, and PR against affected workloads will be initiated without manual intervention. Where compliance policy permits, recommended compensating controls in the interim include restricting network access to the Dalfox server port via network policy or firewall rules to trusted internal addresses only, avoiding deployment of Dalfox in server mode on internet-reachable hosts, and using the --api-key flag to add a credential barrier even before a code-level fix is available.
Metrics
- CVSS v3.1
- 10.0
- Severity
- CRITICAL
- Fixed in
- —
- Affected Products
- 1
- hahwul / dalfox< 2.13.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H