CVE-2026-59270: Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces
Spring Security's embedded UnboundID LDAP server (UnboundIdContainer) unconditionally registers an administrative credential and binds its listener to all available network interfaces.
Spring Security 7.1.0
Spring Security 7.0.0 - 7.0.6
Spring Security 6.5.0 - 6.5.11
Spring Security 6.4.0 - 6.4.18
Spring Security 5.8.0 - 5.8.27
Spring Security 5.7.0 - 5.7.25
Security readout for executives and security teams
Plain-English summary
Affected Spring Security applications can expose an embedded LDAP server to the network with a known administrative identity and credential. An unauthenticated remote attacker could potentially gain administrative LDAP access, compromising directory data and disrupting dependent services.
Executive priority
Treat reachable instances as an immediate remediation priority because compromise requires no existing account or user action. First identify internet-facing and broadly accessible environments, contain listener access, then apply Spring's documented fixed release when confirmed.
Technical view
UnboundIdContainer creates an administrative credential unconditionally and binds the embedded UnboundID LDAP listener to all available network interfaces. In affected releases, this creates a network-reachable, hard-coded credential weakness classified as CWE-798, with potential confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where an affected Spring Security release starts UnboundIdContainer and network controls permit access to its LDAP listener. Merely depending on Spring Security does not establish exposure; runtime configuration and reachability must be verified.
Exploitation context
The CVSS 3.1 score is 9.4, reflecting remote, low-complexity access without privileges or user interaction. The supplied sources do not report active exploitation, and the CVE is not listed as KEV.
Researcher notes
Affected ranges supplied are 7.1.0; 7.0.0–7.0.6; 6.5.0–6.5.11; 6.4.0–6.4.18; 5.8.0–5.8.27; and 5.7.0–5.7.25. No fixed versions or vendor-specific workaround details are included in the supplied bundle, so current Spring guidance must be consulted.
Mitigation direction
Check Spring's advisory for fixed releases and upgrade to a vendor-designated version.
Disable or remove UnboundIdContainer where the embedded LDAP server is unnecessary.
Restrict LDAP listener access using host, container, and network controls until remediation is complete.
Rotate potentially exposed LDAP credentials and review affected directory data after containment.
Validation and detection
Inventory applications using the affected Spring Security version ranges.
Determine whether UnboundIdContainer is instantiated in production or other reachable environments.
Verify the LDAP listener's bound interfaces and network reachability from untrusted segments.
Review LDAP authentication logs for unexpected administrative binds or directory changes.
Confirm remediation prevents unintended network access and removes the known administrative credential risk.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.