Skip to content
Fencer Intel
high 8.1

CVE-2025-11621 json

Vault AWS auth method bypass due to AWS client cache

published last yr. modified 24d ago also BIT-vault-2025-11621 , EUVD-2025-35715 , GHSA-9g4h-h484-3578 , GO-2025-4070

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/hashicorp/vault 1.21.0
  • bitnami vault 1.21.0
  • HashiCorp Vault 1.21.0
  • HashiCorp Vault Enterprise 1.16.27, 1.19.11, 1.20.5, 1.21.0
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251105T184115-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15710-1

Is CVE-2025-11621 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 Fencer

Vendor 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-11621 updated cvss 8.1

github.com/hashicorp/vault: Vault AWS auth method bypass due to AWS client cache

  • Red Hat OpenShift Container Platform 4 openshift4/oc-mirror-plugin-rhel9
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Trusted Artifact Signer rhtas/rekor-backfill-redis-rhel9
    affected: workaround, no fix available
  • Red Hat Zero Trust Workload Identity Manager - Tech Preview zero-trust-workload-identity-manager/spiffe-spire-agent-rhel9, zero-trust-workload-identity-manager/spiffe-spire-server-rhel9, zero-trust-workload-identity-manager/spiffe-spire-oidc-discovery-provider-rhel9
    affected: workaround, no fix available, no fix planned “Will not fix”
  • Red Hat OpenShift Pipelines 1.2 openshift-pipelines 1772694865
    fixed: vendor fix RHSA-2026:3827
  • Red Hat Trusted Artifact Signer 1.3 rhtas 0.0.2-1763550444, rhtas 1.3.1-1763543131, rhtas 1.3.1-1763543194, rhtas 1.3.1-1763545685, rhtas 1.3.1-1763545956, rhtas 1.3.1-1763546693, +2 more
    fixed: vendor fix RHSA-2025:21988
  • Red Hat cert-manager Operator for Red Hat OpenShift cert-manager/cert-manager-operator-rhel9, cert-manager/jetstack-cert-manager-rhel9, cert-manager/cert-manager-istio-csr-rhel9, cert-manager/cert-manager-operator-bundle, cert-manager/jetstack-cert-manager-acmesolver-rhel9 Red Hat Custom Metric Autoscaler operator for Red Hat Openshift custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9, custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9, custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator, custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel9
    not affected: vulnerable code not in execute path
  • Red Hat External Secrets Operator for Red Hat OpenShift external-secrets-operator/external-secrets-rhel9, external-secrets-operator/external-secrets-operator-rhel9 Red Hat external secrets operator for Red Hat OpenShift - Tech Preview external-secrets-operator/external-secrets-rhel9, external-secrets-operator/external-secrets-operator-rhel9
    not affected: vulnerable code not present
  • Red Hat OpenShift Container Platform 4 openshift4/ose-installer-rhel9, openshift4/ose-installer-altinfra-rhel9, openshift4/ose-kube-state-metrics-rhel9, openshift4/ose-baremetal-installer-rhel9, openshift4/ose-installer-artifacts-rhel9
    not affected: component not present
show 2 more
  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel9-operator, +3 more
    not affected: vulnerable code not in execute path
  • Red Hat OpenShift Pipelines 1.2 openshift-pipelines 1771921696, openshift-pipelines 1772679439 Red Hat OpenStack Platform 18.0 rhoso-operators/openstack-rhel9-operator, rhoso-operators/openstack-operator-bundle Red Hat Trusted Artifact Signer 1.3 rhtas 1.3.1-1763545636
    not affected: vulnerable code not present

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.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=0.6.0, <1.21.0
1.21.0
bitnami vault
>=0.6.0, <1.21.0
1.21.0

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-288 Authentication Bypass Using an Alternate Path or Channel

References

Sources

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.