Loading vulnerability…
CVE-2026-41720 is an improper-authentication vulnerability in Spring LDAP DirContextAuthenticationStrategy implementations. Affected implementations do not reject LDAP bind attempts that pair a non-empty username with an empty or null password. Under RFC 4513, this combination constitutes an unauthenticated bind. Where the target LDAP server permits unauthenticated binds, Spring LDAP authentication flows using AbstractContextSource, LdapTemplate, or LdapClient can accept the request without password verification, bypassing intended authentication controls. Affected releases are Spring LDAP 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; unsupported versions may also be affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authentication bypass vulnerability in Spring LDAP verification logic that may allow unauthorized access when a valid username is paired with an empty or null password.
An authentication bypass vulnerability in Spring LDAP where a valid username combined with an empty or null password may be accepted as an unauthenticated bind on LDAP servers that permit such binds, allowing password verification bypass.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.