Is github.com/hashicorp/vault 1.21 vulnerable?
Go · 5 releases from 1.21.0 to 1.21.4 · latest github.com/hashicorp/vault is 1.21.4 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. github.com/hashicorp/vault 1.21.4, the last 1.21 release, is affected by 8 known security advisories (3 high, 1 medium, 4 low), including CVE-2026-5807, CVE-2026-4525, CVE-2026-3605. At least one has no fixed release yet.
Is your project on an affected github.com/hashicorp/vault?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/hashicorp/vault 1.21.4
HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service in github.com/hashicorp/vault
- Affected
- >=0.10.0
- Fixed in
- No fix released
HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization in github.com/hashicorp/vault
- Affected
- >=0.11.2
- Fixed in
- No fix released
HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations in github.com/hashicorp/vault
- Affected
- All versions
- Fixed in
- No fix released
HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS in github.com/hashicorp/vault
- Affected
- >=1.14.0
- Fixed in
- No fix released
HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations
- Affected
- <=1.21.4
- Fixed in
- No fix released
HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization
- Affected
- >=0.11.2 <=1.21.4
- Fixed in
- No fix released
HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service
- Affected
- >=0.10.0 <=1.21.4
- Fixed in
- No fix released
HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS
- Affected
- >=1.14.0 <=1.21.4
- Fixed in
- No fix released
Every github.com/hashicorp/vault 1.21.x release
Affected: 1.21.0 to 1.21.4.
| Version | Known advisories |
|---|---|
| github.com/hashicorp/vault 1.21.4 | CVE-2026-3605, CVE-2026-4525, CVE-2026-5807, CVE-2026-5052, CVE-2026-5807, CVE-2026-4525, CVE-2026-3605, CVE-2026-5052 |
| github.com/hashicorp/vault 1.21.3 | CVE-2026-3605, CVE-2026-4525, CVE-2026-5807, CVE-2026-5052, CVE-2026-5807, CVE-2026-4525, CVE-2026-3605, CVE-2026-5052 |
| github.com/hashicorp/vault 1.21.2 | CVE-2026-3605, CVE-2026-4525, CVE-2026-5807, CVE-2026-5052, CVE-2026-5807, CVE-2026-4525, CVE-2026-3605, CVE-2026-5052 |
| github.com/hashicorp/vault 1.21.1 | CVE-2026-3605, CVE-2026-4525, CVE-2026-5807, CVE-2026-5052, CVE-2026-5807, CVE-2026-4525, CVE-2026-3605, CVE-2026-5052 |
| github.com/hashicorp/vault 1.21.0 | CVE-2026-3605, CVE-2026-4525, CVE-2026-5807, CVE-2026-5052, CVE-2026-5807, CVE-2026-4525, CVE-2026-3605, CVE-2026-5052 |
Which of your client projects are still on github.com/hashicorp/vault 1.21?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/hashicorp/vault version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/hashicorp/vault versions
- github.com/hashicorp/vault 1.20
- github.com/hashicorp/vault 1.19
- github.com/hashicorp/vault 1.18
- github.com/hashicorp/vault 1.17
- github.com/hashicorp/vault 1.16
- github.com/hashicorp/vault 0.11
- github.com/hashicorp/vault 0.10
- github.com/hashicorp/vault 0.9
- github.com/hashicorp/vault 0.8
- github.com/hashicorp/vault 0.7
- github.com/hashicorp/vault 0.6
- All github.com/hashicorp/vault 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.