CVE-2025-3879: Hashicorp Vault Community vulnerable to Incorrect Authorization
Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the boundlocations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.
Published May 2, 2025 · Updated May 6, 2025
Affected packages
github.com/hashicorp/vault
- Ecosystem
- Go
- Affected
- >= 1.10.0, < 1.19.1
- Fixed in
- 1.19.1
- Check
go list -m github.com/hashicorp/vault
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-3605
HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service
high8.1No fixApr 17, 2026CVE-2026-4525
HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization
high7.5No fixApr 17, 2026CVE-2026-5052
HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS
medium5.3No fixApr 17, 2026CVE-2026-5807
HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations
high7.5No fixApr 17, 2026CVE-2025-11621
HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass
high8.1Oct 23, 2025CVE-2025-12044
Hashicorp Vault and Vault Enterprise vulnerable to a denial of service when processing JSON
high7.5Oct 23, 2025
