CVE-2025-11621: HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass

CVE-2025-11621 · Severity: high · CVSS 8.1 · Published 2025-10-23

Vault and Vault Enterprise’s (“Vault”) AWS Auth method may be susceptible to authentication bypass if the role of the configured bound_principal_iam is the same across AWS accounts, or uses a wildcard. This vulnerability, CVE-2025-11621, is fixed in Vault Community Edition 1.21.0 and Vault Enterprise 1.21.0, 1.20.5, 1.19.11, and 1.16.27

Technologies: github.com/hashicorp/vault (Go), HashiCorp Vault. Vendors: Go, HashiCorp.

Quick answers

Is CVE-2025-11621 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-11621 being exploited in the wild.
How severe is CVE-2025-11621?
High severity, with a CVSS score of 8.1, published 23 October 2025.
Which products and versions are affected?
github.com/hashicorp/vault (Go) SEMVER:introduced=0.6.0,fixed=1.21.0.
Is there a fix for CVE-2025-11621?
Yes. github.com/hashicorp/vault (Go): upgrade to 1.21.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-11621?
Check whether you run github.com/hashicorp/vault (Go) or HashiCorp Vault at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/hashicorp/vault (Go): upgrade to 1.21.0 or later
    go get github.com/hashicorp/vault@v1.21.0

Affected products

  • github.com/hashicorp/vault (Go) SEMVER:introduced=0.6.0,fixed=1.21.0
  • HashiCorp Vault

Identifiers

  • CVE-2025-11621
  • GHSA-9g4h-h484-3578
  • GO-2025-4070

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.