Skip to main content
VulnerabilityPublished Updated

CVE-2026-33320: TomWright dasel · Uncontrolled Recursion

Affects TomWright daselSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 3.3.2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade dasel and github.com/tomwright/dasel to 3.3.2.

Affected software

ProductAffectedFixed in
TomWrightdaselAffected
  • >=3.0.0 <3.3.2
Fixed in
  • 3.3.2
Gogithub.com/tomwright/daselpkg:golang/github.com/tomwright/daselOther threatsAffected
  • >=3.0.0 <3.3.2
Fixed in
  • 3.3.2

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

AI-suggested

To mitigate CVE-2026-33320, organizations should upgrade dasel to version 3.3.2 or later, where the uncontrolled recursion issue has been patched. For environments where immediate upgrade is not feasible, implement input validation and sanitization to restrict or reject untrusted YAML inputs containing alias nodes. Limit the use of dasel to trusted data sources and avoid processing YAML from unverified or external origins. Monitor resource usage of processes invoking dasel to detect abnormal CPU or memory consumption indicative of exploitation attempts. Incorporate rate limiting or sandboxing techniques to isolate dasel executions and prevent system-wide impact. Additionally, review automation workflows to ensure YAML inputs are controlled and consider adding static analysis or scanning tools to detect potentially malicious YAML structures. Maintain awareness of updates from the dasel project and apply security patches promptly. Finally, document and train development and operations teams about this vulnerability to reduce inadvertent exposure.

Description

Dasel is a command-line tool and library for querying, modifying, and transforming data structures. Starting in version 3.0.0 and prior to version 3.3.1, Dasel's YAML reader allows an attacker who can supply YAML for processing to trigger extreme CPU and memory consumption. The issue is in the library's own `UnmarshalYAML` implementation, which manually resolves alias nodes by recursively following `yaml.Node.Alias` pointers without any expansion budget, bypassing go-yaml v4's built-in alias expansion limit. Version 3.3.2 contains a patch for the issue.

References

Community reviews

Loading reviews…