VYPR
Medium severity6.5NVD Advisory· Published Jun 8, 2026

CVE-2026-11611

CVE-2026-11611

Description

389 Directory Server's Content Synchronization plugin can cause denial of service via unbounded memory growth or crashes.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

389 Directory Server's Content Synchronization plugin can cause denial of service via unbounded memory growth or crashes.

Vulnerability

The Content Synchronization (syncrepl) persistent search plugin in 389 Directory Server is vulnerable to denial of service. An authenticated client can open a persistent sync search and then stop reading responses, leading to unbounded memory growth as modification events queue without limit until memory exhaustion and a server crash. Additional race conditions in the plugin's thread lifecycle can cause crashes during connection teardown or shutdown. This vulnerability exists in code present since the plugin's introduction [2].

Exploitation

An attacker needs to be an authenticated client. The attacker opens a persistent sync search and then stops reading the responses. This triggers the unbounded queue growth. Race conditions leading to crashes can occur during connection teardown or server shutdown [2].

Impact

Successful exploitation can lead to a denial of service due to memory exhaustion and server crashes. The scope of the compromise is the availability of the 389 Directory Server instance [2].

Mitigation

No upstream fix is available as of 2026-04-22. The vulnerable code has been present since the plugin's introduction. Affected versions are not explicitly listed, but the issue is confirmed on UBI 8 and CentOS Stream 8 production binaries [2].

AI Insight generated on Jun 8, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

3

News mentions

0

No linked articles in our index yet.