Is github.com/tomwright/dasel/v3 3.0 vulnerable?
Go · 1 release from 3.0.0 to 3.0.0 · latest github.com/tomwright/dasel/v3 is 3.11.2 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. github.com/tomwright/dasel/v3 3.0.0, the last 3.0 release, is affected by 10 known security advisories (2 high, 3 medium, 5 low), including CVE-2026-46378, CVE-2026-46377, CVE-2026-62866. At least one has no fixed release yet.
Is your project on an affected github.com/tomwright/dasel/v3?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/tomwright/dasel/v3 3.0.0
Dasel: Selector lexer panics on trailing whitespace in `parseCurRune` in github.com/tomwright/dasel
- Affected
- >=3.0.0 <3.11.2
- Fixed in
- 3.11.2
Dasel: Unbounded recursion in JSON and XML readers causes unrecoverable stack-overflow DoS in github.com/tomwright/dasel
- Affected
- >=3.0.0 <3.11.1
- Fixed in
- 3.11.1
Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`
- Affected
- >=3.0.0 <3.11.2
- Fixed in
- 3.11.2
Dasel: Unbounded recursion in JSON and XML readers causes unrecoverable stack-overflow DoS
- Affected
- >=3.0.0 <3.11.1
- Fixed in
- 3.11.1
Dasel: Index-out-of-range panic in dasel selector lexer on trailing backslash in quoted string in github.com/tomwright/dasel
- Affected
- >=3.0.0
- Fixed in
- No fix released
Dasel: Denial of service in dasel selector lexer due to infinite loop on unterminated regex literal in github.com/tomwright/dasel
- Affected
- >=3.0.0 <3.10.1
- Fixed in
- 3.10.1
Dasel: Denial of service in dasel selector lexer due to infinite loop on unterminated regex literal
- Affected
- >=3.0.0 <3.10.1
- Fixed in
- 3.10.1
Dasel: Index-out-of-range panic in dasel selector lexer on trailing backslash in quoted string
- Affected
- >=3.0.0 <=3.10.0
- Fixed in
- No fix released
Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service in github.com/tomwright/dasel
- Affected
- >=3.0.0 <3.3.2
- Fixed in
- 3.3.2
Dasel has unbounded YAML alias expansion in dasel leads to CPU/memory denial of service
- Affected
- >=3.0.0 <3.3.2
- Fixed in
- 3.3.2
Which of your client projects are still on github.com/tomwright/dasel/v3 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/tomwright/dasel/v3 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/tomwright/dasel/v3 versions
- github.com/tomwright/dasel/v3 3.3
- github.com/tomwright/dasel/v3 3.2
- github.com/tomwright/dasel/v3 3.1
- github.com/tomwright/dasel/v3 3.11
- github.com/tomwright/dasel/v3 3.10
- github.com/tomwright/dasel/v3 3.9
- github.com/tomwright/dasel/v3 3.8
- github.com/tomwright/dasel/v3 3.7
- github.com/tomwright/dasel/v3 3.6
- All github.com/tomwright/dasel/v3 advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.