Advisoriesby IbisVaultGHSA-f9ch-h8j7-8jwg
Hashicorp Vault Community vulnerable to Incorrect Authorization
Fix: upgrade to 1.19.1 or later
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
Hashicorp Vault has Login MFA Rate Limit Bypass VulnerabilityCVE-2025-6015fixed in 1.20.1Hashicorp Vault's TOTP Secrets Engine Susceptible to Code ReuseCVE-2025-6014fixed in 1.20.1Hashicorp Vault has Lockout Feature Authentication BypassCVE-2025-6004fixed in 1.20.1Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing UsersCVE-2025-6011fixed in 1.20.1Vault Community Edition rekey and recovery key operations can cause denial of serviceCVE-2025-4656fixed in 1.20.0Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive InformationCVE-2025-4166fixed in 1.19.3