Quick answers
- Is CVE-2026-103880 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103880 being exploited in the wild.
- How severe is CVE-2026-103880?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Apache Directory Ldap Api 2.1.0 before 2.1.9.
- Is there a fix for CVE-2026-103880?
- 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-103880 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-103880?
- 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
The vulnerability is an asymmetric resource consumption flaw in bcrypt password handling within Apache Directory LDAP API versions 2.1.0 through 2.1.8. An attacker can supply a bcrypt cost parameter (e.g., 30) that forces the server to perform intensive CPU operations during password verification, consuming server resources and degrading performance. No authentication or special access is required; the attack can be triggered during password storage or verification operations in LDAP directory services.
Affected products
- Apache Directory LDAP API 2.1.0 before 2.1.9
Timeline
- 2026-10-02: disclosed
- 2026-10-02: patched