VaultGHSA-f9ch-h8j7-8jwg
Hashicorp Vault Community vulnerable to Incorrect Authorization
Medium6.6CVE-2025-3879 · Published May 2, 2025 · updated May 7, 2025
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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/vault Go | >= 1.10.0, < 1.19.1 | 1.19.1 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-863
- Also known as
- BIT-vault-2025-3879, CVE-2025-3879, GO-2025-3662
More Vault advisories
All Vault| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 12025 | Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability Medium5.7Aug 1, 2025 | Medium5.7 | 1.20.1 |
| Aug 12025 | Hashicorp Vault's TOTP Secrets Engine Susceptible to Code ReuseMedium6.5Aug 1, 2025 | Medium6.5 | 1.20.1 |
| Aug 12025 | Hashicorp Vault has Lockout Feature Authentication BypassMedium5.3Aug 1, 2025 | Medium5.3 | 1.20.1 |
| Aug 12025 | Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing UsersLow3.7Aug 1, 2025 | Low3.7 | 1.20.1 |
| Jun 262025 | Vault Community Edition rekey and recovery key operations can cause denial of serviceLow3.1Jun 26, 2025 | Low3.1 | 1.20.0 |
| May 22025 | Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive InformationMedium4.5May 2, 2025 | Medium4.5 | 1.19.3 |