Uncontrolled Memory Allocation Affecting apache-directory-api package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-APACHEDIRECTORYAPI-20414093
- published3 Oct 2026
- disclosed2 Oct 2026
Introduced: 2 Oct 2026
NewCVE-2026-102731 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest apache-directory-api.
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache-directory-api package and not the apache-directory-api package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.
A malicious peer (or a MITM) can send a small BER-encoded response causing a large memory allocation before any data is received. This can lead to an OutOfMemoryError and denial of service.
The client JVM OOMs (OutOfMemoryError bypasses the DecoderException handlers) or pins the large allocation per connection while the attacker stalls.
A handful of connections exhausts any heap. The same bytes from an unauthenticated pre-bind client hit any embedding server that did not set MAX_PDU_SIZE_ATTR.
This issue affects Apache Directory LDAP API: from 1.2.0 before 1.2.9.
Users are recommended to upgrade to version 1.2.9, which fixes the issue.