CVE-2025-3879 json
Vault’s Azure Authentication Method bound_location Restriction Could be Bypassed on Login
published last yr. modified 2mo ago also BIT-vault-2025-3879 , EUVD-2025-13121 , GHSA-f9ch-h8j7-8jwg , GO-2025-3662
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/hashicorp/vault 1.19.1
- bitnami vault 1.19.1
- HashiCorp Vault 1.19.1
- HashiCorp Vault Enterprise 1.16.16, 1.17.13, 1.18.6, 1.19.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250506T153719-1.1
opensuse advisories openSUSE-SU-2025:15059-1
Is CVE-2025-3879 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-3879 updated cvss 6.6
vault: Vault’s Azure Authentication Method bound_location Restriction Could be Bypassed on Login
-
Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operatoraffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/vault | >=1.10.0, <1.19.1 |
1.19.1 |
| bitnami | vault | >=0.10.0, <1.19.1 |
1.19.1 |
Affected products
- HashiCorp Vault
- HashiCorp Vault Enterprise
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
discuss.hashicorp.com
/t/hcsec-2025-07-vault-s-azure-authentication-method-bound-location-restriction-could-be-bypassed-on-login/747
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-3879
advisory, web
-
github.com
/hashicorp/vault
package
-
pkg.go.dev
/vuln/GO-2025-3662
web
-
github.com
/advisories/GHSA-f9ch-h8j7-8jwg
advisory
Sources
- CVE List CVE-2025-3879
- GitHub Advisory GHSA-f9ch-h8j7-8jwg
- NVD CVE-2025-3879
- OSV BIT-vault-2025-3879
- OSV GO-2025-3662
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.