Skip to content
statance
MenuClose
Log inStart for free ↗
medium · CVSS 6.5

CVE-2026-78701

389-ds-base: 389-ds-base: cve-2026-11610 incomplete fix may introduce a connection-stall dos

Published 25 Aug 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in 389-ds-base. A remote, authenticated attacker could exploit a vulnerability in the Simple Authentication and Security Layer (SASL) UNBIND process. By sending a specially crafted request, the attacker can cause a connection to stall, leading to resource exhaustion and a Denial of Service (DoS) for the server.

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-baseRed Hatunaffected: 0:3.2.0-10.el10_2 to < *See vendor advisory
389-ds-baseRed Hatunaffected: 0:2.8.0-10.el9_8 to < *See vendor advisory
dirsrv/dirsrv-container-rhel10Red Hatunaffected: 1788851765 to < *See vendor advisory
redhat-ds:11/389-ds-baseRed HatDefault status: affectedSee 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: affectedSee vendor advisory
389-ds-baseRed HatDefault status: affectedSee vendor advisory
389-ds:1.4/389-ds-baseRed HatDefault status: affectedSee 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