Quick answers
- Is CVE-2026-42568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42568 being exploited in the wild.
- How severe is CVE-2026-42568?
- Medium severity, with a CVSS score of 4.3, published 10 June 2026.
- Which products and versions are affected?
- org.yamcs:yamcs-core (Maven) < 5.12.7, ECOSYSTEM:introduced=0,fixed=5.12.7; Yamcs < 5.12.7, < 5.12.7, < 5.13.0.
- Is there a fix for CVE-2026-42568?
- Yes. org.yamcs:yamcs-core (Maven): upgrade to 5.12.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42568 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-42568?
- Check whether you run org.yamcs:yamcs-core (Maven) or Yamcs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.yamcs:yamcs-core (Maven): upgrade to 5.12.7 or later
# set org.yamcs:yamcs-core to 5.12.7 in your pom.xml or build.gradle
Technical details
An LDAP injection vulnerability exists in `org.yamcs.security.LdapAuthModule` due to improper neutralization of the username parameter before it is inserted into an LDAP search filter. Specifically, the code fails to apply RFC 4515 escaping, allowing characters like wildcards (*) to be processed by the LDAP server. An attacker with a known valid password can use a wildcard username (e.g., '*') to authenticate as the first user returned by the LDAP directory, leading to horizontal privilege escalation. This issue is reachable over the network via the authentication endpoint and has been patched in versions 5.12.7 and 5.13.0.
Affected products
- Yamcs Yamcs < 5.12.7, < 5.13.0
Identifiers
- CVE-2026-42568
- GHSA-cqh3-jg8p-336j
Timeline
- 2026-05-21: patched: Versions 5.12.7 and 5.13.0 released
- 2026-06-10: disclosed: CVE-2026-42568 published