CVE-2026-42568 json
Yamcs Vulnerable to LDAP Injection in LdapAuthModule
published 5mo ago modified 3mo ago also EUVD-2026-36196 , GHSA-cqh3-jg8p-336j
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 1
- Exploit-DB
Summary
Yamcs is a mission control framework. Prior to versions 5.13.0 and 5.12.7, an LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` when constructing search filters. The username parameter is inserted directly into the LDAP filter without proper RFC 4515 escaping. Versions 5.13.0 and 5.12.7 patch the issue.
Patch / fix
- maven org.yamcs:yamcs-core 5.12.7
- org.yamcs yamcs-core 5.12.7
- spaceapplications yamcs 5.12.7
Is CVE-2026-42568 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-52603)
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-52603 YAMCS yamcs-core 5.12.7 - LDAP Injection webapps, 2026-05-30
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.yamcs:yamcs-core | <5.12.7 |
5.12.7 |
Affected products
- yamcs yamcs
Classification
- Weakness
-
- CWE-90 Improper Neutralization of Special Elements used in an LDAP Query
References
Sources
- CVE List CVE-2026-42568
- GitHub Advisory GHSA-cqh3-jg8p-336j
- NVD CVE-2026-42568
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.