Dalfox Server Mode has an Unauthenticated Arbitrary File Read with Out-of-Band Exfiltration via custom-payload-file
CVE-2026-45088GHSA-35wr-x7v6-9fv2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/hahwul/dalfox/v2 2.13.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
Go github.com/hahwul/dalfox/v2
- Affected
- <= 2.12.0
- Fixed in
- 2.13.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-35wr-x7v6-9fv2 lists affected ranges: Go github.com/hahwul/dalfox/v2 >=0 <=2.12.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-45088: 0.31% estimated exploitation activity in the next 30 days; percentile 23.98 (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.
Summary When dalfox is run in REST API server mode, the custom-payload-file field in model.Options is JSON-tagged and deserialized directly from the attacker's request body, then propagated unchanged through dalfox.Initialize into the scan engine. The engine passes the value to voltFile.ReadLinesOrLiteral, which reads lines from any file path accessible to the dalfox process and embeds each line as an XSS payload in outbound HTTP requests directed at the attacker-controlled target URL. Because the server has no API key by default, an unauthenticated network attacker can exfiltrate the contents of arbitrary files on the dalfox host by reading them line-by-line through scan traffic. Severity High (CVSS 3.1: 7.5) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Attack Vector: Network — server binds to 0.0.0.0:6664 by default; reachable by any network peer. - Attack Complexity: Low — no preconditions beyond network access; skip-discovery and param are both attacker-supplied, so the code…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-35wr-x7v6-9fv2
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-2026-45088 Advisory: Dalfox Server Mode has an Unauthenticated Arbitrary File Read with Out-of-Band Exfiltration via `custom-payload-file` IDs: CVE-2026-45088, GHSA-35wr-x7v6-9fv2 Record: https://patchnext.com/advisories/cve-2026-45088 (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 7.5) 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-35wr-x7v6-9fv2 (GitHub-reviewed advisory GHSA-35wr-x7v6-9fv2 lists affected ranges: Go github.com/hahwul/dalfox/v2 >=0 <=2.12.0) Commands are suggestions: review each one before running it.
Loading voting…