Skip to content
Fencer Intel
medium 6.2

CVE-2026-62866 json

Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`

published last mo. modified last mo. also EUVD-2026-84016 , GHSA-65gg-g7rw-6cpc , GO-2026-6548

cvss
6.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/tomwright/dasel/v3 3.11.2
  • tomwright dasel 3.11.2
  • dasel Debian 14 3.11.2-1

debian advisories DEBIAN-CVE-2026-62866

Is CVE-2026-62866 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/TomWright/dasel/security/advisories/GHSA-65gg-g7rw-6cpc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/tomwright/dasel/v3
>=3.0.0, <3.11.2
3.11.2
go github.com/tomwright/dasel
all versions
 no fix listed
go github.com/tomwright/dasel/v2
all versions
 no fix listed

Affected products

  • TomWright dasel

Classification

Weakness
  • CWE-129 Improper Validation of Array Index

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.