CVE-2026-62866
MediumCVSS 6.2Summary
Dasel versions 3.0.0 through 3.11.2 have a bug in the tokenizer that reads out of bounds when a selector ends with whitespace, causing a panic and process termination. Input passed through Tokenize() or dasel.Query is also affected.
Risk Assessment
This can lead to denial of service (DoS) as an attacker can craft a selector that crashes the application or tool.
Recommendation
Update Dasel to version 3.11.2, which includes a fix for this out-of-bounds read.
Other vulnerabilities in Dasel
See all- CVE-2026-59168Medium
Dasel versions 3.0.0 through 3.11.1 lack a depth limit when parsing nested JSON or XML. Deeply nested attacker-controlled input can exhaust the Go goroutine stack and cause an unrecoverable fatal error that terminates the entire process.
- CVE-2026-46378Medium
A vulnerability in Dasel versions 3.0.0 through 3.10.1 causes an infinite loop when tokenizing an unterminated regex literal (e.g., r/). An attacker can exploit a crafted selector string to exhaust CPU resources.
- CVE-2026-46377Medium
Dasel versions 3.0.0 through 3.10.0 have a vulnerability in the parseCurRune function of the tokenizer that fails to perform bounds checking when processing escape sequences in quoted strings. An attacker can supply a crafted selector string, causing an index-out-of-range panic.
Original NVD description (English source)
Dasel is a command-line tool and library for querying, modifying, and transforming data structures. From 3.0.0 until 3.11.2, selector/lexer/tokenize.go parseCurRune advances the input index across trailing whitespace and then reads the source at the exhausted index without an end-of-input check. A selector ending in whitespace, including input passed through lexer.NewTokenizer(...).Tokenize() or dasel.Query, can therefore cause an index-out-of-range panic and terminate the process. This issue is fixed in version 3.11.2.