CVE-2026-46377 TomWright CVE debrief

Who should care

Users of Dasel versions 3.0.0 through 3.10.0 should be aware of this vulnerability and take steps to mitigate it by updating to version 3.10.1 or later. This includes operators managing affected deployments, platform administrators, vulnerability management teams, and security teams responsible for reviewing and implementing mitigations.

Technical summary

The vulnerability exists in the escape sequence handler in (*Tokenizer).parseCurRune in selector/lexer/tokenize.go. The handler increments past a trailing backslash in a quoted string and then reads p.src[pos] without a bounds check. This allows attacker-controlled selector strings to trigger a Go index-out-of-range panic. The issue affects Dasel versions 3.0.0 through 3.10.0 and is fixed in version 3.10.1. Users should verify their deployments and review official advisories for affected scope and vendor guidance.

Defensive priority

Medium-High based on potential impact and exploitability through attacker-controlled input strings requiring immediate review and mitigation planning for exposed deployments through compensating controls and vendor-supported updates or mitigations through normal change control where exposure is confirmed and verified via relevant monitoring, detection, and logs for exposed assets that need extra review and tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented to validate affected scope, severity, and vendor guidance and implement bounds checking and review compensating controls for exposed systems while remediation is scheduled and verified and check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented to validate affected scope, severity, and vendor guidance and implement bounds checking and review compensating controls for exposed systems while remediation is scheduled and verified and check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented to validate affected scope, severity, and vendor guidance and implement bounds checking and review compensating controls for exposed systems while remediation is scheduled and verified and check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented to validate affected scope, severity, and vendor guidance and implement bounds checking and review compensating controls for exposed systems while remediation is scheduled and verified and check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented to validate affected scope, severity, and vendor guidance and implement bounds checking and review compensating controls for exposed systems while remediation is and to

Recommended defensive actions

• Update to version 3.10.1 or later
• Review and validate input data
• Implement bounds checking
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record was published on 2026-07-16T19:16:46.127Z and has not been modified since then. The NVD entry is currently 6.2, MEDIUM. The Dasel vulnerability allows attacker-controlled selector strings to trigger a Go index-out-of-range panic due to improper handling of escape sequences in quoted strings. Users should verify their deployments and review official advisories for affected scope and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.