Is github.com/hashicorp/vault 1.16 vulnerable?
Go · 4 releases from 1.16.0 to 1.16.3 · latest github.com/hashicorp/vault is 1.21.4 · checked 18 Nov 2026
Yes: 40 known advisories
Yes. github.com/hashicorp/vault 1.16.3, the last 1.16 release, is affected by 40 known security advisories (1 critical, 9 high, 8 medium, 22 low), including CVE-2025-6000, CVE-2026-5807, CVE-2026-4525. 4 more affect earlier 1.16.x releases. 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.16.3
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
HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass in github.com/hashicorp/vault
- Affected
- >=0.6.0 <1.21.0
- Fixed in
- 1.21.0
HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass
- Affected
- >=0.6.0 <1.21.0
- Fixed in
- 1.21.0
HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads in github.com/hashicorp/vault
- Affected
- <1.20.3
- Fixed in
- 1.20.3
HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads
- Affected
- <1.20.3
- Fixed in
- 1.20.3
Hashicorp Vault has Incorrect Validation for Non-CA Certificates in github.com/hashicorp/vault
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Privilege Escalation Vulnerability in github.com/hashicorp/vault
- Affected
- >=0.10.4 <1.20.0
- Fixed in
- 1.20.0
Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration in github.com/hashicorp/vault
- Affected
- >=0.8.0 <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users in github.com/hashicorp/vault
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Lockout Feature Authentication Bypass in github.com/hashicorp/vault
- Affected
- >=1.13.0 <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault's TOTP Secrets Engine Susceptible to Code Reuse in github.com/hashicorp/vault
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability in github.com/hashicorp/vault
- Affected
- >=1.10.0 <1.20.1
- Fixed in
- 1.20.1
HashiCorp Vault ldap auth method may not have correctly enforced MFA in github.com/hashicorp/vault
- Affected
- <1.20.2
- Fixed in
- 1.20.2
HashiCorp Vault ldap auth method may not have correctly enforced MFA
- Affected
- <1.20.2
- Fixed in
- 1.20.2
Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration
- Affected
- >=0.8.0 <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Privilege Escalation Vulnerability
- Affected
- >=0.10.4 <1.20.0
- Fixed in
- 1.20.0
Hashicorp Vault has Incorrect Validation for Non-CA Certificates
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Lockout Feature Authentication Bypass
- Affected
- >=1.13.0 <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault's TOTP Secrets Engine Susceptible to Code Reuse
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability
- Affected
- >=1.10.0 <1.20.1
- Fixed in
- 1.20.1
Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users
- Affected
- <1.20.1
- Fixed in
- 1.20.1
Vault Community Edition rekey and recovery key operations can cause denial of service in github.com/hashicorp/vault
- Affected
- >=1.14.8 <1.20.0
- Fixed in
- 1.20.0
Vault Community Edition rekey and recovery key operations can cause denial of service
- Affected
- >=1.14.8 <1.20.0
- Fixed in
- 1.20.0
Hashicorp Vault Community vulnerable to Incorrect Authorization in github.com/hashicorp/vault
- Affected
- >=1.10.0 <1.19.1
- Fixed in
- 1.19.1
Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive Information in github.com/hashicorp/vault
- Affected
- >=0.3.0 <1.19.3
- Fixed in
- 1.19.3
Hashicorp Vault Community vulnerable to Incorrect Authorization
- Affected
- >=1.10.0 <1.19.1
- Fixed in
- 1.19.1
Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive Information
- Affected
- >=0.3.0 <1.19.3
- Fixed in
- 1.19.3
Hashicorp Vault vulnerable to denial of service through memory exhaustion in github.com/hashicorp/vault
- Affected
- >=1.2.0 <1.18.1
- Fixed in
- 1.18.1
Hashicorp Vault vulnerable to denial of service through memory exhaustion
- Affected
- >=1.2.0 <1.18.1
- Fixed in
- 1.18.1
Vault Community Edition privilege escalation vulnerability in github.com/hashicorp/vault
- Affected
- <1.18.0
- Fixed in
- 1.18.0
Vault Community Edition privilege escalation vulnerability
- Affected
- <1.18.0
- Fixed in
- 1.18.0
Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default in github.com/hashicorp/vault
- Affected
- >=1.7.7 <1.17.6
- Fixed in
- 1.17.6
Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
- Affected
- >=1.7.7 <1.17.6
- Fixed in
- 1.17.6
Fixed within 1.16.x, affecting earlier releases
Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions in github.com/hashicorp/vault
- Affected
- >=1.10.0 <1.16.3 · >=1.17.0-rc1 <1.17.2
- Fixed in
- 1.16.3, 1.17.2
Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions
- Affected
- >=1.10.0 <1.15.12 · >=1.16.0-rc1 <1.16.3 · >=1.17.0-rc1 <1.17.2
- Fixed in
- 1.15.12, 1.16.3, 1.17.2
HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims in github.com/hashicorp/vault
- Affected
- >=0.11.0 <1.16.3 · >=1.17.0-rc1 <1.17.0
- Fixed in
- 1.16.3, 1.17.0
HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims
- Affected
- >=1.17.0-rc1 <1.17.0 · >=1.16.0-rc1 <1.16.3 · >=0.11.0 <1.15.9
- Fixed in
- 1.15.9, 1.16.3, 1.17.0
Every github.com/hashicorp/vault 1.16.x release
Affected: 1.16.0 to 1.16.3. Latest github.com/hashicorp/vault: 1.21.4.
| Version | Known advisories |
|---|---|
| github.com/hashicorp/vault 1.16.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, CVE-2025-11621, CVE-2025-11621, CVE-2025-6203, CVE-2025-6203, CVE-2025-6037, CVE-2025-5999, CVE-2025-6000, CVE-2025-6011, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6013, CVE-2025-6013, CVE-2025-6000, CVE-2025-5999, CVE-2025-6037, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6011, CVE-2025-4656, CVE-2025-4656, CVE-2025-3879, CVE-2025-4166, CVE-2025-3879, CVE-2025-4166, CVE-2024-8185, CVE-2024-8185, CVE-2024-9180, CVE-2024-9180, CVE-2024-7594, CVE-2024-7594 |
| github.com/hashicorp/vault 1.16.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, CVE-2025-11621, CVE-2025-11621, CVE-2025-6203, CVE-2025-6203, CVE-2025-6037, CVE-2025-5999, CVE-2025-6000, CVE-2025-6011, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6013, CVE-2025-6013, CVE-2025-6000, CVE-2025-5999, CVE-2025-6037, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6011, CVE-2025-4656, CVE-2025-4656, CVE-2025-3879, CVE-2025-4166, CVE-2025-3879, CVE-2025-4166, CVE-2024-8185, CVE-2024-8185, CVE-2024-9180, CVE-2024-9180, CVE-2024-7594, CVE-2024-7594, CVE-2024-6468, CVE-2024-6468, CVE-2024-5798, CVE-2024-5798 |
| github.com/hashicorp/vault 1.16.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, CVE-2025-11621, CVE-2025-11621, CVE-2025-6203, CVE-2025-6203, CVE-2025-6037, CVE-2025-5999, CVE-2025-6000, CVE-2025-6011, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6013, CVE-2025-6013, CVE-2025-6000, CVE-2025-5999, CVE-2025-6037, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6011, CVE-2025-4656, CVE-2025-4656, CVE-2025-3879, CVE-2025-4166, CVE-2025-3879, CVE-2025-4166, CVE-2024-8185, CVE-2024-8185, CVE-2024-9180, CVE-2024-9180, CVE-2024-7594, CVE-2024-7594, CVE-2024-6468, CVE-2024-6468, CVE-2024-5798, CVE-2024-5798 |
| github.com/hashicorp/vault 1.16.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, CVE-2025-11621, CVE-2025-11621, CVE-2025-6203, CVE-2025-6203, CVE-2025-6037, CVE-2025-5999, CVE-2025-6000, CVE-2025-6011, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6013, CVE-2025-6013, CVE-2025-6000, CVE-2025-5999, CVE-2025-6037, CVE-2025-6004, CVE-2025-6014, CVE-2025-6015, CVE-2025-6011, CVE-2025-4656, CVE-2025-4656, CVE-2025-3879, CVE-2025-4166, CVE-2025-3879, CVE-2025-4166, CVE-2024-8185, CVE-2024-8185, CVE-2024-9180, CVE-2024-9180, CVE-2024-7594, CVE-2024-7594, CVE-2024-6468, CVE-2024-6468, CVE-2024-5798, CVE-2024-5798 |
Which of your client projects are still on github.com/hashicorp/vault 1.16?
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.19
- github.com/hashicorp/vault 1.18
- github.com/hashicorp/vault 1.17
- github.com/hashicorp/vault 1.15
- github.com/hashicorp/vault 1.14
- github.com/hashicorp/vault 1.13
- github.com/hashicorp/vault 1.21
- github.com/hashicorp/vault 1.20
- github.com/hashicorp/vault 0.11
- github.com/hashicorp/vault 0.10
- github.com/hashicorp/vault 0.9
- github.com/hashicorp/vault 0.8
- 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.