Read the docs
TI-2025-03426 Aliases CVE-2025-3879GHSA-f9ch-h8j7-8jwg

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

Priority MEDIUM 40CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · NVD. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-863.

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00445 38th percentileScored 2026-11-07
Fix Partial Vault (HashiCorp): 1.19.1Vault Enterprise (HashiCorp): 1.19.1+1 more productRed Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
HashiCorpVault0.10.0 to before 1.19.11.19.1Patch availableCNA
HashiCorpVault Enterprise0.10.0 to before 1.19.11.19.1Patch availableCNA
—github.com/hashicorp/vault (Go)1.10.0 to before 1.19.11.19.1Patch availableGHSA-f9ch-h8j7-8jwg
  • Vault VendorHashiCorp Affected 0.10.0 to before 1.19.1 Fixed in 1.19.1 Patch available CNA
  • Vault Enterprise VendorHashiCorp Affected 0.10.0 to before 1.19.1 Fixed in 1.19.1 Patch available CNA
  • github.com/hashicorp/vault (Go) Vendor— Affected 1.10.0 to before 1.19.1 Fixed in 1.19.1 Patch available GHSA-f9ch-h8j7-8jwg

CPE configurations NVD · 4

CPEVersionsRoleVendor
cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*0.10.0 to before 1.16.18VulnerableHashiCorp
cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*0.10.0 to before 1.19.1VulnerableHashiCorp
cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*1.17.0 to before 1.17.14; 1.18.0 to before 1.18.7VulnerableHashiCorp
cpe:2.3:a:hashicorp:vault:1.19.0:*:*:*:enterprise:*:*:*1.19.0VulnerableHashiCorp
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:* Versions 0.10.0 to before 1.16.18 Vulnerable ·HashiCorp
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:* Versions 0.10.0 to before 1.19.1 Vulnerable ·HashiCorp
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:* Versions 1.17.0 to before 1.17.14; 1.18.0 to before 1.18.7 Vulnerable ·HashiCorp
  • cpe:2.3:a:hashicorp:vault:1.19.0:*:*:*:enterprise:*:*:* Versions 1.19.0 Vulnerable ·HashiCorp

Remediation

  • Fix · CNA Vault (HashiCorp) Fixed in 1.19.1
  • Fix · CNA Vault Enterprise (HashiCorp) Fixed in 1.19.1
  • Fix · GHSA-f9ch-h8j7-8jwg github.com/hashicorp/vault (Go) Fixed in 1.19.1 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Openshift Data Foundation 4AffectedNo fix yet: Fix deferred

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-3879
  2. 2026-10-03 Alias added: GHSA-f9ch-h8j7-8jwg

References

  • TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
  • TI-2022-19053 An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. CVSS 3.1CRITICAL 9.1
  • TI-2020-17874 The official vault docker images before 0.11.6 contain a blank password for a root user. CVSS 3.1CRITICAL 9.8
  • TI-2020-10142 HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP… CVSS 3.1CRITICAL 9.8
  • TI-2026-04407 Vault Vulnerable to Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS CVSS 3.1HIGH 8.6
  • TI-2025-05421 Arbitrary Remote Code Execution via Plugin Catalog Abuse CVSS 3.1CRITICAL 9.1
See all 71 →

Sources