Skip to content
Fencer Vulns
medium 6.5

CVE-2025-6013 json

Vault LDAP MFA Enforcement Bypass When Using Username As Alias

published 2025-08-06 15 mo ago modified 2026-09-10 1 mo ago also BIT-vault-2025-6013 , EUVD-2025-23817 , GHSA-7rx2-769v-hrwf , GO-2025-3848

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

Summary

Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if username_as_alias was set to true and a user had multiple CNs that are equal but with leading or trailing spaces. Fixed in Vault Community Edition 1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.

Patch / fix

  • go github.com/hashicorp/vault 1.20.2
  • bitnami vault 1.20.2
  • HashiCorp Vault 1.20.2
  • HashiCorp Vault Enterprise 1.16.24, 1.18.13, 1.19.8, 1.20.2
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250814T182633-150000.1.98.1

suse advisories SUSE-SU-2025:02912-1

  • openbao openSUSE Tumbleweed 2.3.2-1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250811T192933-1.1

opensuse advisories openSUSE-SU-2025:15460-1openSUSE-SU-2025:15434-1

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-6013 updated cvss 6.5

github.com/hashicorp/vault: Vault LDAP MFA Bypass

  • Red Hat cert-manager Operator for Red Hat OpenShift cert-manager/cert-manager-operator-rhel9, cert-manager/jetstack-cert-manager-rhel9, cert-manager/jetstack-cert-manager-acmesolver-rhel9 Red Hat external secrets operator for Red Hat OpenShift - Tech Preview external-secrets-operator/external-secrets-operator-rhel9
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator Red Hat Trusted Artifact Signer rhtas/fulcio-rhel9, rhtas/client-server-rhel9
    affected: workaround, no fix planned “Will not fix”

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
15 mo ago

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
NVD 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
<1.20.2
1.20.2
bitnami vault
>=1.10.0, <1.20.2
1.20.2

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-156 Improper Neutralization of Whitespace

References

Sources

Fencer Vulns 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.