Quick answers
- Is CVE-2026-103885 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103885 being exploited in the wild.
- How severe is CVE-2026-103885?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Apache Directory Ldap Api 2.1.0 to 2.1.8.
- Is there a fix for CVE-2026-103885?
- Yes: fixed in 2.1.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103885 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-103885?
- Check whether you run Apache Directory Ldap Api 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
- Fixed in: 2.1.9
Technical details
This is an asymmetric resource consumption vulnerability in the LDAP API's telephone number parsing logic. A remote attacker can send an LDAP message containing a malformed telephone number attribute that triggers infinite or extremely long-running regex or parsing logic, consuming CPU indefinitely. No authentication is required; the attack succeeds on any exposed LDAP server using the vulnerable library versions.
Affected products
- Apache Directory LDAP API 2.1.0 to 2.1.8
Timeline
- 2026-10-02: disclosed