CVE-2026-41720GHSA-JRV5-8W28-4265
Authentication Bypass with Empty Password in Spring LDAP
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.4.5, 3.2.18, 3.3.7.1, 4.0.3.1, 4.0.4, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- Spring Spring LDAP
From 2.4.0 · fixed in 2.4.5; From 3.2.0 · fixed in 3.2.18; From 3.3.0 · fixed in 3.3.7.1; From 4.0.0 · fixed in 4.0.3.1
- org.springframework.ldap:spring-ldap-coreMaven
From 4.0.0 · fixed in 4.0.4
- org.springframework.ldap:spring-ldap-coreMaven
From 3.3.0 · fixed in 3.3.8
- org.springframework.ldap:spring-ldap-coreMaven
From 3.2.0 · through 3.2.16
- org.springframework.ldap:spring-ldap-coreMaven
through 2.4.4