Is github.com/hashicorp/boundary 0.20 vulnerable?
Go · 3 releases from 0.20.0 to 0.20.3 · latest github.com/hashicorp/boundary is 0.21.3 · checked 18 Nov 2026
No known advisories in the last release
github.com/hashicorp/boundary 0.20.3, the last 0.20 release, has no known advisories. 2 advisories affect earlier 0.20.x releases, so update to 0.20.3.
go get github.com/hashicorp/boundary@v0.20.3Is your project on an affected github.com/hashicorp/boundary?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 0.20.x, affecting earlier releases
Hashicorp Boundary workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes in github.com/hashicorp/boundary
- Affected
- <0.19.5 · >=0.20.0 <0.20.3 · >=0.21.0 <0.21.3
- Fixed in
- 0.19.5, 0.20.3, 0.21.3
Hashicorp Boundary workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes
- Affected
- <0.19.5 · >=0.20.0 <0.20.3 · >=0.21.0 <0.21.3
- Fixed in
- 0.19.5, 0.20.3, 0.21.3
Every github.com/hashicorp/boundary 0.20.x release
Affected: 0.20.0 to 0.20.1. 0.20.3 is not affected. Latest github.com/hashicorp/boundary: 0.21.3.
| Version | Known advisories |
|---|---|
| github.com/hashicorp/boundary 0.20.3 | None |
| github.com/hashicorp/boundary 0.20.1 | CVE-2026-7776, CVE-2026-7776 |
| github.com/hashicorp/boundary 0.20.0 | CVE-2026-7776, CVE-2026-7776 |
Which of your client projects are still on github.com/hashicorp/boundary 0.20?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/hashicorp/boundary version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/hashicorp/boundary versions
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.