CVE-2026-41720

Authentication Bypass with Empty Password in Spring LDAP

Published Jun 9, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
Description
Spring LDAP's DirContextAuthenticationStrategy implementations do not reject a bind request where a non-empty username is paired with an empty or null password.

Affected versions:
Spring LDAP 2.4.0 through 2.4.4; 3.2.0 through 3.2.17; 3.3.0 through 3.3.7; 4.0.0 through 4.0.3.

Analysis

AI-generated

Technical impact

Spring LDAP's DirContextAuthenticationStrategy implementations allow a credential bind request that supplies a non‑empty user identifier but an empty or null password to succeed, effectively bypassing authentication. The vulnerability constitutes improper authentication (CWE‑287) and can lead to unauthorized access to LDAP data and services, potentially exposing sensitive directory information. Since the flaw exists in the authentication layer, the impact is confined to applications using Spring LDAP and does not affect the underlying LDAP server beyond the binding operation.

Affected Systems

Affected vendors and products include Spring's Spring LDAP library, versions 2.4.0 through 2.4.4, 3.2.0 through 3.2.17, 3.3.0 through 3.3.7, and 4.0.0 through 4.0.3. Applications that rely on these specific releases and construct authentication strategies without additional password validation are potentially vulnerable. The flaw does not affect other Spring projects that do not use the DirContextAuthenticationStrategy.

Risk and Exploitability

The CVSS score of 7.4 highlights a high severity level, and while the EPSS score is not currently available, current estimates suggest a low exploitation likelihood. The vulnerability is not listed in the CISA KEV catalogue, which indicates no public knowledge of active exploitation at the time of this assessment. Attackers would need network or application access capable of sending a bind request with a valid username and an empty password, which is a relatively low‑barrier attack but still requires the target to allow LDAP bind operations from that source.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring LDAP to a patched release that detaches the default DirContextAuthenticationStrategy from accepting empty or null passwords – any release newer than 4.0.3, 3.3.7, 3.2.17, or 2.4.4 for the involved Spring LDAP major version.
  • If upgrading is not immediately feasible, implement a custom authentication strategy that explicitly rejects empty or null passwords before delegating to the underlying LDAP bind.
  • Configure the LDAP server or application to disallow empty password binds, ensuring that authentication requests require a non‑empty credential, and enforce strict password policies.
  • Regularly review dependency versions and apply security patches from Spring promptly.

Generated by OpenCVE AI on June 9, 2026 at 05:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jrv5-8w28-4265 Spring LDAP has Authentication Bypass with Empty Password
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Ldap
Vendors & Products Spring
Spring spring Ldap
Type Values Removed Values Added
Description Spring LDAP's DirContextAuthenticationStrategy implementations do not reject a bind request where a non-empty username is paired with an empty or null password. Affected versions: Spring LDAP 2.4.0 through 2.4.4; 3.2.0 through 3.2.17; 3.3.0 through 3.3.7; 4.0.0 through 4.0.3.
Title Authentication Bypass with Empty Password in Spring LDAP
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jun 23, 2026, 8:47 PM
Reserved
Apr 22, 2026, 6:21 AM
Status
Awaiting Analysis
Published
Jun 9, 2026, 5:16 AM
Modified
Jul 23, 2026, 8:10 AM