389-ds-base-2.8.0-7.el9_8

389 Directory Server is an LDAP version 3 (LDAPv3) compliant server. The base packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration.

Security Fix(es):

* 389-ds-base: 389-ds-base: unbounded LDAP controls count in get_ldapmessage_controls_ext() causes CPU and heap amplification (remote DoS) (CVE-2026-9064)

Bug Fix(es) and Enhancement(s):

* Getting "build_candidate_list - Database error 11" messages after migrating to LMDB. [rhel-9.8.z] (JIRA:RHEL-152356)
* Web console doesn't show the sub suffix of ou=foo,ou=people,dc=example,dc=com. [rhel-9.8.z] (JIRA:RHEL-168967)
* DS 12 does not handle escape char in bind user [rhel-9.8.z] (JIRA:RHEL-170269)
* [RFE] Add OS-level thread names to all server threads [rhel-9.8.z] (JIRA:RHEL-174524)
* Online export is failing when using the option "-s" [rhel-9.8.z] (JIRA:RHEL-180716)
* Server shutdown during online reindex may lead to data loss [rhel-9.8.z] (JIRA:RHEL-183895)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

CVE-2026-9064
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls within the default maximum BER message size (2 MB), causing excessive CPU consumption and heap allocation on the server. Under concurrent exploitation, this leads to significant latency degradation, worker thread starvation, or out-of-memory termination, resulting in a denial of service.