CVE-2026-59168: TomWright dasel · Uncontrolled Recursion
Affects TomWright daselSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium : upgrade to 3.11.1 when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.11.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Upgrade dasel and github.com/tomwright/dasel to 3.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TomWrightdasel | Affected
| Fixed in
|
Gogithub.com/tomwright/daselpkg:golang/github.com/tomwright/daselOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade dasel to version 3.11.1 or later, where this uncontrolled recursion issue has been fixed. No other mitigations are indicated or effective since the failure cannot be intercepted by defer or recover, and input size limits do not prevent the stack exhaustion.
Description
CVE-2026-59168 is a medium severity vulnerability in TomWright dasel versions from 3.0.0 up to but not including 3.11.1. It involves uncontrolled recursion in JSON and XML parsing functions that can cause the Go goroutine stack to be exhausted, leading to a fatal error that terminates the process. The issue arises because the parsing functions recurse once per input nesting level without a depth guard. The XML input-size limit does not prevent this stack exhaustion, and the failure cannot be intercepted by defer or recover mechanisms. This vulnerability has been fixed in version 3.11.1.