CVE-2025-11621: Vault AWS auth method bypass due to AWS client cache
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: HashiCorp Vault 1.21.0; HashiCorp Vault Enterprise 1.16.27, 1.19.11, 1.20.5.
Low priority for now. Upgrade to HashiCorp Vault 1.21.0; HashiCorp Vault Enterprise 1.16.27, 1.19.11, 1.20.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Oct 23, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-288
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HashiCorp
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | vault | cpe:2.3:a:hashicorp:vault |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Vault
- 0.6.0 and later · before 1.21.0affected · semver
HashiCorp Vault Enterprise
- 0.6.0 and later · before 1.21.0affected · semverfixed in 1.20.5, 1.19.11, 1.16.27
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp vault0.6.0 and later · before 1.16.27
- hashicorp vault0.6.0 and later · before 1.21.0
- hashicorp vault1.18.0 and later · up to 1.18.15 inclusive
- hashicorp vault1.19.0 and later · before 1.19.11
- hashicorp vault1.20.0 and later · before 1.20.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/hashicorp/vault | from 0.6.0 · before 1.21.0 | 1.21.0 |
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.40Plan
- CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates39Monitor
- CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-6013Aug 6, 2025 · Vault LDAP MFA Enforcement Bypass When Using Username As Alias32Monitor
- ← EarlierCVE-2025-6203Aug 28, 2025 · Vault unauthenticated denial of service through complex json payload30Monitor
- Later →CVE-2025-12044Oct 23, 2025 · Vault Vulnerable to Denial of Service Due to Rate Limit Regression30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Vault | 1.21.0 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.16.27 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.19.11 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.20.5 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.21.0 | Vendor (CNA) |
| Go:github.com/hashicorp/vault | 1.21.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3605176 days apartVault KVv2 Metadata and Secret Deletion Policy Bypass Denial-of-Service32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2025-600083 days apartArbitrary Remote Code Execution via Plugin Catalog Abuse36Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-288 · Authentication Bypass Using an Alternate Path or ChannelCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.