CVE-2025-3879

Vault’s Azure Authentication Method bound_location Restriction Could be Bypassed on Login

Description

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.

Category

6.6
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.05%
Affected: HashiCorp Vault
Affected: HashiCorp Vault Enterprise
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-3879?
CVE-2025-3879 has been scored as a medium severity vulnerability.
How to fix CVE-2025-3879?
To fix CVE-2025-3879, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-3879 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-3879 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-3879?
CVE-2025-3879 affects HashiCorp Vault, HashiCorp Vault Enterprise.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.