Account impersonation via unescaped LDAP username
Published Jun 10, 2026 · Updated Jun 10, 2026
LDAP injection in Space Applications Services Yamcs before 5.12.7 allows remote authenticated users to impersonate an LDAP account. LdapAuthModule replaces the {0} placeholder in its LDAP search filter with the username without RFC 4515 escaping, so wildcard input changes the query. Exploitation requires LDAP authentication and one valid password; username=* returns the first directory user sharing that password, exposing that account's access.
Summary
What happened
LDAP injection in Space Applications Services Yamcs before 5.12.7 allows remote authenticated users to impersonate an LDAP account. LdapAuthModule replaces the {0} placeholder in its LDAP search filter with the username without RFC 4515 escaping, so wildcard input changes the query. Exploitation requires LDAP authentication and one valid password; username=* returns the first directory user sharing that password, exposing that account's access.
The record
- CVE
- CVE-2026-42568
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Space Applications Services
- Product
- Yamcs
- Classifications
- CWE-90, CAPEC-136, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.12.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cqh3-jg8p-336j username wildcard proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo