NIXPKGS-2026-2703
GitHub issue
published 13 hours ago
Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`
Permalink
CVE-2026-62866
6.2 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): None (N)
- Integrity (I): None (N)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): None (N)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): None (N)
- Modified Availability (MA): High (H)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse accepted
- @LeSuisse published on GitHub
Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`
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.
References
-
https://github.com/TomWright/dasel/security/advisories/GHSA-65gg-g7rw-6cpc exploitx_refsource_CONFIRM
-
https://github.com/TomWright/dasel/releases/tag/v3.11.2 x_refsource_MISC
Affected products
dasel
- ==>= 3.0.0, < 3.11.2
Package maintainers
-
@0x4A6F Joachim Ernst <mail-maintainer@0x4A6F.dev>