Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 7.5

CVE-2026-9064

389-ds-base: 389-ds-base: unbounded ldap controls count in get_ldapmessage_controls_ext() causes cpu and heap amplification (remote dos)

Published 20 May 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-06 16:14 UTC

Statance checks for CVE-2026-9064. Connected servers are checked automatically against the fixed versions their distribution or package ecosystem has published for it, including app dependency lockfiles. Check my servers ↗
Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
389-ds-baseaffected: 0See vendor advisory
redhat-ds:11Red Hatunaffected: 8060020260609102432.0ca98e7e to < *See vendor advisory
redhat-ds:11Red Hatunaffected: 8080020260610130252.f969626e to < *See vendor advisory
redhat-ds:11Red Hatunaffected: 8100020260601104139.37ed7c03 to < *See vendor advisory
redhat-ds:12Red Hatunaffected: 9020020260615123354.1674d574 to < *See vendor advisory
redhat-ds:12Red Hatunaffected: 9040020260611130021.1674d574 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:3.2.0-7.el10_2 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:3.0.6-18.el10_0 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:1.3.11.1-12.el7_9 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8100020260601102239.25e700aa to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8040020260609102422.96015a92 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8040020260609102422.96015a92 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8060020260609102416.824efc52 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8060020260609102416.824efc52 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8080020260610125847.6dbb3803 to < *See vendor advisory
389-ds:1.4Red Hatunaffected: 8080020260610125847.6dbb3803 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:2.8.0-7.el9_8 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:2.2.4-18.el9_2 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:2.4.5-25.el9_4 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:2.6.1-21.el9_6 to < *See vendor advisory
dirsrv/dirsrv-container-rhel10Red Hatunaffected: 1781714123 to < *See vendor advisory
redhat-ds:12/389-ds-baseRed HatDefault status: affectedSee vendor advisory
389-ds-baseRed HatDefault status: affectedSee vendor advisory
389-ds-baseRed HatDefault status: unknownSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed