Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4fcp-jxh7-23x8 | Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service |
Thu, 26 Mar 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 25 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:tomwright:dasel:*:*:*:*:*:go:*:* |
Tue, 24 Mar 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tomwright
Tomwright dasel |
|
| Vendors & Products |
Tomwright
Tomwright dasel |
Tue, 24 Mar 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service | |
| Weaknesses | CWE-674 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-26T12:24:32.421Z
Reserved: 2026-03-18T21:23:36.677Z
Link: CVE-2026-33320
Updated: 2026-03-26T12:24:27.905Z
Status : Analyzed
Published: 2026-03-24T01:17:02.203
Modified: 2026-03-25T16:08:49.057
Link: CVE-2026-33320
No data.
OpenCVE Enrichment
Updated: 2026-03-25T20:40:45Z
Github GHSA