CVE-2026-41720: CWE-287: Improper Authentication in Spring Spring LDAP
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.
AI Analysis
Technical Summary
Spring LDAP's DirContextAuthenticationStrategy implementations fail to properly validate authentication attempts by accepting bind requests with a non-empty username and an empty or null password. This improper authentication (CWE-287) affects 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. The CVSS 3.1 base score is 7.4, indicating a high severity vulnerability with network attack vector, high complexity, no privileges required, no user interaction, and impacts confidentiality and integrity but not availability. No patch or official remediation level has been disclosed by the vendor as of the publication date.
Potential Impact
Successful exploitation could allow an attacker to bypass authentication controls by submitting a bind request with a valid username but no password, potentially leading to unauthorized access and compromise of confidentiality and integrity of the LDAP service. Availability is not impacted. There are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider additional access controls or monitoring around LDAP authentication attempts to detect anomalous bind requests with empty passwords. Avoid deploying affected versions in sensitive environments without compensating controls.
CVE-2026-41720: CWE-287: Improper Authentication in Spring Spring LDAP
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.
CVSS v3.1
Score 7.4high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Spring LDAP's DirContextAuthenticationStrategy implementations fail to properly validate authentication attempts by accepting bind requests with a non-empty username and an empty or null password. This improper authentication (CWE-287) affects 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. The CVSS 3.1 base score is 7.4, indicating a high severity vulnerability with network attack vector, high complexity, no privileges required, no user interaction, and impacts confidentiality and integrity but not availability. No patch or official remediation level has been disclosed by the vendor as of the publication date.
Potential Impact
Successful exploitation could allow an attacker to bypass authentication controls by submitting a bind request with a valid username but no password, potentially leading to unauthorized access and compromise of confidentiality and integrity of the LDAP service. Availability is not impacted. There are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider additional access controls or monitoring around LDAP authentication attempts to detect anomalous bind requests with empty passwords. Avoid deploying affected versions in sensitive environments without compensating controls.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-22T06:21:37.021Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a279b2ee29bf47b50357512
Added to database: 6/9/2026, 4:48:46 AM
Last enriched: 6/9/2026, 5:04:34 AM
Last updated: 6/9/2026, 11:58:49 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.