Skip to content
Fencer Intel
medium 5.3

CVE-2025-6004 json

Vault Userpass and LDAP User Lockout Bypass

published last yr. modified last mo. also BIT-vault-2025-6004 , EUVD-2025-23396 , GHSA-qgj7-fmq2-6cc4 , GO-2025-3840

cvss
5.3
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 40%
public exploits
0
none known

Summary

Vault and Vault Enterprise’s (“Vault”) user lockout feature could be bypassed for Userpass and LDAP authentication methods. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

Patch / fix

  • go github.com/hashicorp/vault 1.20.1
  • bitnami vault 1.20.1
  • HashiCorp Vault 1.20.1
  • HashiCorp Vault Enterprise 1.16.23, 1.18.12, 1.19.7, 1.20.1
  • 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

Is CVE-2025-6004 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-6004 updated cvss 5.3

github.com/hashicorp/vault: Vault Userpass/LDAP Lockout Bypass Vulnerability

  • 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 available “Fix deferred”
  • 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
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

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

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts

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.