# CVE-2026-45087: Dalfox: Unauthenticated Remote Code Execution via `found-action` in Dalfox Server Mode

> Unauthenticated attackers can execute arbitrary shell commands on the host by sending malicious JSON to the Dalfox server API.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-v25v-m36w-jp4h, GO-2026-5649

## What is CVE-2026-45087?

CVE-2026-45087 is a critical command injection vulnerability in hahwul dalfox, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-306 (Missing Authentication for Critical Functionality), CWE-15 (External Control of System or Configuration Setting)

## Which versions are affected by CVE-2026-45087?

4 open source packages ship an affected version, including github.com/hahwul/dalfox/v2 and github.com/hahwul/dalfox.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hahwul/dalfox/v2` | Go | All versions | 2.13.0 |
| `github.com/hahwul/dalfox/v2` | Go | All versions | 2.13.0 |
| `github.com/hahwul/dalfox/v2` | Go | All versions | 2.13.0 |
| `github.com/hahwul/dalfox` | Go | All versions | None |

## How do I fix CVE-2026-45087?

Upgrade github.com/hahwul/dalfox/v2 to 2.13.0 or later.

## Is CVE-2026-45087 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45087 exists.

Public exploit code:

- Dalfox Found-Action Deserialization RCE (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45087 and fix it if it is affected.

What it is: CVE-2026-45087 is a critical command injection vulnerability in hahwul dalfox, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45087 exists.

Affected packages and fixed versions:
- github.com/hahwul/dalfox/v2 (Go): affected all versions; fixed in 2.13.0
- github.com/hahwul/dalfox/v2 (Go): affected all versions; fixed in 2.13.0
- github.com/hahwul/dalfox/v2 (Go): affected all versions; fixed in 2.13.0
- github.com/hahwul/dalfox (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45087/ (Markdown: https://insights.sbomify.com/CVE-2026-45087/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45087
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45087
- OSV: https://osv.dev/vulnerability/CVE-2026-45087

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45087/
Summaries are generated and may contain mistakes; the official description above is the record.