Description
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.
Published: 2026-09-21
Score: 6.2 Medium
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Patch
AI Analysis

Impact

Dasel is a command‑line utility that parses selector expressions. Between versions 3.0.0 and 3.11.2 the lexer function parseCurRune advances past trailing whitespace and then accesses the input slice at the exhausted index without checking the end of the string. This causes an integer out‑of‑bounds read that triggers a panic and terminates the process. The flaw is a classic integer bounds error (CWE‑129) and results in a local denial of service where any supplied selector ending in whitespace can crash the runner.

Affected Systems

The vulnerability affects TomWright’s Dasel utility, specifically all releases from 3.0.0 up to and including 3.11.2. Version 3.11.2 and later contain a fix, so the risk applies to users running an earlier, unpatched release.

Risk and Exploitability

The CVSS score of 6.2 indicates a moderate severity. No EPSS score is available and the issue is not listed in CISA KEV, but the bug is known and could be triggered by any adversary who can supply a selector with trailing whitespace to a running Dasel instance. If Dasel is executed with elevated privileges or as part of a service, an attacker could cause the service to terminate, leading to a denial of availability. The attack vector is local; there is no identified mechanism for remote exploitation or code injection, so the risk is confined to denial of service with privileged contexts giving potential collateral impact.

Generated by OpenCVE AI on September 21, 2026 at 18:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Dasel to version 3.11.2 or newer, which contains the lexer boundary check patch.
  • If an upgrade is not immediately possible, limit the input scope of Dasel or its library to trusted selectors and reject any selector containing trailing whitespace to avoid triggering the panic.
  • Monitor system logs for panic or crash events that may indicate attempts to exploit the flaw and consider disabling or sandboxing Dasel until the patch is applied.

Generated by OpenCVE AI on September 21, 2026 at 18:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 21 Sep 2026 17:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`
Weaknesses CWE-129
References
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-21T18:00:18.178Z

Reserved: 2026-07-14T21:10:50.032Z

Link: CVE-2026-62866

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-21T17:17:38.053

Modified: 2026-09-21T18:17:09.753

Link: CVE-2026-62866

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T18:30:17Z

Weaknesses
  • CWE-129

    Improper Validation of Array Index