Dasel Security Update Addresses 2 Vulnerabilities
Tech GuruQuick Answer
Dasel 3.11.2 is the combined update target for two denial-of-service flaws. Version 3.11.1 fixes unbounded JSON/XML reader recursion; 3.11.2 fixes a selector lexer panic on trailing whitespace. Applications embedding Dasel must update and redeploy their own binary, not only replace a separately installed CLI.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Dasel v3 CLI and library consumers, identify untrusted document and selector inputs, and update to 3.11.2 through the project's supported release path.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Dasel packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-cqxr-jxr2-85pq / GHSA-65gg-g7rw-6cpc |
| CVEs | CVE-2026-59168, CVE-2026-62866 |
| Project advisory publication | 2026-06-27 15:00:01-15:05:45 UTC (two advisories) |
| Recorded source timestamp (historical snapshot) | 2026-09-22 19:52:17 UTC |
| Affected versions | github.com/tomwright/dasel/v3 >= 3.0.0, <= 3.11.0; github.com/tomwright/dasel/v3 >= 3.0.0, < 3.11.2 |
| Fixed version | 3.11.1 fixes CVE-2026-59168; 3.11.2 fixes CVE-2026-62866 and is the combined target. |
| CVSS base score | 6.2 (CVSS v3) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
CVE-2026-59168 lets excessive JSON/XML nesting exhaust the Go stack; this is a fatal runtime error that recover() cannot catch. An XML byte-size cap does not also impose a depth limit. CVE-2026-62866 is a separate out-of-range lexer access after skipping trailing whitespace, reachable through CLI queries and library selectors.
What To Validate Now
- Inventory. Locate Dasel packages and release streams identified in the project advisories deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: github.com/tomwright/dasel/v3 >= 3.0.0, <= 3.11.0; github.com/tomwright/dasel/v3 >= 3.0.0, < 3.11.2 Do not infer applicability from product family or severity alone.
- Remediate. Update affected v3 installations and library dependencies to 3.11.2, rebuild consumers and redeploy. Do not stop at 3.11.1 when untrusted selectors can reach the lexer.
- Validate. Use an isolated process with resource limits to check ordinary JSON/XML, controlled depth-limit cases and trailing-whitespace selectors. Confirm expected errors or results without process termination; no crash test was run here.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
