# CVE-2025-3879: Vault’s Azure Authentication Method bound_location Restriction Could be Bypassed on Login

> Attackers can bypass Azure authentication location restrictions in HashiCorp Vault by exploiting improper token claim validation during login.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2025
- **Updated:** 2 May 2025
- **Also known as:** BIT-vault-2025-3879, GHSA-f9ch-h8j7-8jwg, GO-2025-3662

## What is CVE-2025-3879?

CVE-2025-3879 is a medium-severity authentication bypass vulnerability in Hashicorp Vault, published on 2 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-3879?

4 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | From 1.10.0 | 1.19.1 |
| `github.com/hashicorp/vault` | Go | From 1.10.0 | 1.19.1 |
| `github.com/hashicorp/vault` | Go | From 1.10.0 | 1.19.1 |
| `vault` | Bitnami | From 0.10.0 | 1.19.1 |

Products: Hashicorp Vault.

## How do I fix CVE-2025-3879?

Upgrade github.com/hashicorp/vault to 1.19.1 or later.

## Is CVE-2025-3879 being exploited?

There is no known exploitation of CVE-2025-3879 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3879 and fix it if it is affected.

What it is: CVE-2025-3879 is a medium-severity authentication bypass vulnerability in Hashicorp Vault, published on 2 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3879 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected from 1.10.0; fixed in 1.19.1
- github.com/hashicorp/vault (Go): affected from 1.10.0; fixed in 1.19.1
- github.com/hashicorp/vault (Go): affected from 1.10.0; fixed in 1.19.1
- vault (Bitnami): affected from 0.10.0; fixed in 1.19.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3879/ (Markdown: https://insights.sbomify.com/CVE-2025-3879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3879
- OSV: https://osv.dev/vulnerability/CVE-2025-3879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3879/
Summaries are generated and may contain mistakes; the official description above is the record.