Skip to main content
VulnerabilityPublished

CVE-2026-45090: hahwul dalfox · Race Condition

Affects hahwul dalfoxSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.13.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.13.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade dalfox and github.com/hahwul/dalfox to 2.13.0.

Affected software

ProductAffectedFixed in
hahwuldalfoxAffected
  • <2.13.0
Fixed in
  • 2.13.0
Gogithub.com/hahwul/dalfoxpkg:golang/github.com/hahwul/dalfoxOther threatsAffected
  • <2.13.0
Fixed in
  • 2.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in dalfox version 2.13.0. Users should upgrade to version 2.13.0 or later to remediate this issue. Until upgrading, avoid running dalfox in server mode with the default configuration lacking an API key, or restrict access to the REST API to trusted users only. Patch status is not explicitly stated in vendor advisory content, but the fix is included in version 2.13.0.

Description

CVE-2026-45090 is a race condition vulnerability in hahwul dalfox versions prior to 2.13.0. The issue arises because two sequential worker stages write to the same results channel, which is closed after the first stage, causing the second stage to write to a closed channel. This triggers a Go runtime panic that crashes the dalfox process. In server mode, this crash can be remotely triggered by unauthenticated callers via the REST API if the default configuration is used without an API key and the attacker supplies POST-body data that is reflected by the target. The vulnerability is fixed in version 2.13.0.

References

Community reviews

Loading reviews…