CVE-2026-33320: Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service

CVE-2026-33320 · Severity: low · CVSS 3.1 · Published 2026-03-23

Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service in github.com/tomwright/dasel

Technologies: github.com/tomwright/dasel (Go), github.com/tomwright/dasel/v2 (Go), github.com/tomwright/dasel/v3 (Go). Vendors: Go.

Quick answers

Is CVE-2026-33320 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33320 being exploited in the wild.
How severe is CVE-2026-33320?
Low severity, with a CVSS score of 3.1, published 23 March 2026.
Which products and versions are affected?
github.com/tomwright/dasel (Go) SEMVER:introduced=0; github.com/tomwright/dasel/v2 (Go) SEMVER:introduced=0; github.com/tomwright/dasel/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.3.2.
Is there a fix for CVE-2026-33320?
Yes. github.com/tomwright/dasel/v3 (Go): upgrade to 3.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33320?
Check whether you run github.com/tomwright/dasel (Go), github.com/tomwright/dasel/v2 (Go) or github.com/tomwright/dasel/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/tomwright/dasel/v3 (Go): upgrade to 3.3.2 or later
    go get github.com/tomwright/dasel/v3@v3.3.2

Affected products

  • github.com/tomwright/dasel (Go) SEMVER:introduced=0
  • github.com/tomwright/dasel/v2 (Go) SEMVER:introduced=0
  • github.com/tomwright/dasel/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.3.2

Identifiers

  • CVE-2026-33320
  • GHSA-4fcp-jxh7-23x8
  • GO-2026-4768

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.