Vault AWS auth method bypass due to AWS client cache
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2025-11621
PublishedVault 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
- Source published
- 23 Oct 2025 19:08:54 UTC
- Source modified
- 26 Feb 2026 16:57:11 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
euvd · EUVD-2025-35715
PublishedVault 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
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 23, 2025, 7:08:54 PM
dateUpdated: Feb 26, 2026, 4:57:11 PM
8 related source bulletins · separate from aliases
WID-SEC-W-2025-2396: Hashicorp Vault: Mehrere Schwachstellen
CVE-2025-11621 · CVE-2025-12044
openSUSE-SU-2025:15710-1: govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media
CVE-2016-11063 · CVE-2016-11066 · CVE-2016-11067 · CVE-2016-11068 · CVE-2016-11069 · CVE-2016-11070 · CVE-2016-11071 · CVE-2016-11072 · CVE-2016-11073 · CVE-2016-11074 · CVE-2016-11075 · CVE-2016-11076 · CVE-2016-11077 · CVE-2016-11078 · CVE-2016-11079 · CVE-2016-11080 · CVE-2016-11081 · CVE-2016-11082 · CVE-2016-11083 · CVE-2016-11084 · CVE-2017-18872 · CVE-2023-32199 · CVE-2024-58269 · CVE-2025-10545 · CVE-2025-10678 · CVE-2025-10954 · CVE-2025-11374 · CVE-2025-11375 · CVE-2025-11579 · CVE-2025-11621 · CVE-2025-12044 · CVE-2025-26625 · CVE-2025-27093 · CVE-2025-41410 · CVE-2025-41443 · CVE-2025-54286 · CVE-2025-54287 · CVE-2025-54288 · CVE-2025-54289 · CVE-2025-54290 · CVE-2025-54291 · CVE-2025-54293 · CVE-2025-54469 · CVE-2025-54470 · CVE-2025-54471 · CVE-2025-54499 · CVE-2025-58073 · CVE-2025-58075 · CVE-2025-58356 · CVE-2025-59043 · CVE-2025-59048 · CVE-2025-59530 · CVE-2025-59836 · CVE-2025-59937 · CVE-2025-61141 · CVE-2025-61524 · CVE-2025-61581 · CVE-2025-61688 · CVE-2025-62156 · CVE-2025-62157 · CVE-2025-62375 · CVE-2025-62506 · CVE-2025-62513 · CVE-2025-62705 · CVE-2025-62714 · CVE-2025-62725 · CVE-2025-62820 · CVE-2025-64101 · CVE-2025-64102 · CVE-2025-64103
RHSA-2025:21988: Red Hat Security Advisory: RHTAS 1.3.1 - Red Hat Trusted Artifact Signer Release
CVE-2025-11621 · CVE-2025-12044
RHSA-2026:3827: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.20.3
CVE-2025-11621 · CVE-2025-12044 · CVE-2025-47913 · CVE-2025-61729 · CVE-2025-66506 · CVE-2025-66564
RHSA-2025:21981: Red Hat Security Advisory: RHTAS 1.3.1 - Red Hat Trusted Artifact Signer Release
CVE-2025-11621 · CVE-2025-12044
RHSA-2025:21984: Red Hat Security Advisory: RHTAS 1.3.1 - Red Hat Trusted Artifact Signer Release
CVE-2025-11621 · CVE-2025-12044
RHSA-2025:21976: Red Hat Security Advisory: RHTAS 1.3.1 - Red Hat Trusted Artifact Signer Release
CVE-2025-11621 · CVE-2025-12044
RHSA-2025:22058: Red Hat Security Advisory: RHTAS 1.3.1 - Tech Preview Release Of the Policy Controller Operator
CVE-2025-11621 · CVE-2025-12044
- Source published
- Oct 23, 2025, 7:08:54 PM (timezone not stated)
- Source modified
- Feb 26, 2026, 4:57:11 PM (timezone not stated)
- Observed here
- 9 Nov 2026 02:10:42 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 3.1 · 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd · CVE-2025-11621
PublishedVault 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
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-288
Original publisher date fields
published: 2025-10-23T19:15:48.893
lastModified: 2026-10-18T21:10:00.120
2 source CPE criteria · context only
- cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
- cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 23 Oct 2025 19:15:48 UTC
- Source modified
- 18 Oct 2026 21:10:00 UTC
- Observed here
- 25 Oct 2026 01:17:23 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Secondary · 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
osv · GHSA-9g4h-h484-3578
PublishedVault 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 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.
- Source published
- 23 Oct 2025 21:31:43 UTC
- Source modified
- 10 Sep 2026 03:50:29 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Publisher rating · HIGH
osv · GO-2025-4070
PublishedHashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass in github.com/hashicorp/vault
- Source published
- 30 Oct 2025 15:02:33 UTC
- Source modified
- 4 Feb 2026 04:38:02 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.