dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-45090

HIGH · 7.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dalfox is a powerful open-source XSS scanner and utility focused on automation. Prior to 2.13.0, ParameterAnalysis in pkg/scanning/parameterAnalysis.go runs two sequential worker stages that both write to the same results channel. The channel is correctly closed after the first stage completes (close(results) at line 438), but the second stage — which processes POST-body parameters (dp) — is then launched with the same already-closed channel as its output. When a scanned parameter is reflected, processParams executes results <- paramResult on the closed channel, triggering a Go runtime panic that crashes the entire dalfox process. In server mode, the crash is remotely triggerable by any unauthenticated caller who can reach the REST API, because the default configuration has no API key and the second stage activates whenever options.Data != "" (i.e., the attacker supplies the data field) and the target reflects at least one parameter. This vulnerability is fixed in 2.13.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Dalfox prior to 2.13.0, ParameterAnalysis runs two sequential worker stages that both write to the same results channel. The channel is closed after the first stage (line 438), but the second stage (processing POST-body parameters) is then launched with this already-closed channel. When a parameter reflects, processParams writes to the closed channel, triggering a Go runtime panic that crashes the entire process. In server mode, unauthenticated attackers can trigger this by supplying the data field against a target that reflects parameters.

MitigationUpgrade to Dalfox version 2.13.0 or later. If unable to upgrade immediately, disable server mode or enforce API authentication to prevent unauthenticated access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Dalfox version
    Run 'dalfox version' or 'dalfox --version' to obtain the installed version number
    Affected if Version is lower than 2.13.0 (e.g., 2.12.0, 2.11.0, etc.)
  2. Determine if server mode is enabled
    Check if Dalfox is running with server mode flags such as '--server', 'server' subcommand, or configured to expose an HTTP API (typically port 8089 or similar)
    Affected if Server mode is active and accepting requests
  3. Verify network exposure of server mode
    Inspect running processes or configuration to confirm the server is bound to a network interface accessible to untrusted users (e.g., 0.0.0.0 vs 127.0.0.1)
    Affected if Server mode is exposed to unauthenticated network access without API key protection
  4. Confirm target reflects parameters
    If server mode is active, test by sending a request with a 'data' field containing a known test string (e.g., 'TESTREFLECT') and observe if the application panics or terminates unexpectedly
    Affected if The target endpoint reflects POST-body parameters back in the response and causes Dalfox to crash

The environment is affected if Dalfox version is below 2.13.0 AND server mode is enabled and accessible to trigger the channel write to a closed channel via reflected parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Dalfox version 2.13.0 or later. If unable to upgrade immediately, disable server mode or enforce API authentication to prevent unauthenticated access.

Recommended fix High confidence

2.13.0

  1. Check the current installed version of dalfox by running 'dalfox version'
  2. Download dalfox version 2.13.0 or later from the official GitHub releases (github.com/hahwul/dalfox/releases)
  3. Replace the existing dalfox binary with the new version
  4. Verify the upgrade was successful by running 'dalfox version' and confirming the version is 2.13.0 or later
  5. If using server mode, ensure API key is configured for production deployments to prevent unauthorized access

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45090 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data