Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-78701

CVE-2026-78701: 389-ds-base SASL UNBIND DoS Vulnerability

CVE-2026-78701 is a denial of service vulnerability in 389-ds-base affecting the SASL UNBIND process. Authenticated attackers can exploit this flaw to cause resource exhaustion. This article covers technical details, impact, and mitigation.

Published:

CVE-2026-78701 Overview

CVE-2026-78701 is a denial-of-service flaw in the 389-ds-base LDAP directory server. A remote, authenticated attacker can exploit the Simple Authentication and Security Layer (SASL) UNBIND process by sending a specially crafted request. The malformed request causes the affected connection to stall, consuming server resources. Repeated exploitation leads to resource exhaustion and denies service to legitimate LDAP clients.

The vulnerability affects the SASL bind teardown path and requires only low-privilege authentication to trigger. Red Hat tracks the issue in Bug Report #2523232 and the Red Hat CVE-2026-78701 Advisory.

Critical Impact

Authenticated attackers can stall server connections through malformed SASL UNBIND requests, causing resource exhaustion and denial of service against directory infrastructure.

Affected Products

  • 389 Directory Server (389-ds-base)
  • Red Hat Directory Server distributions bundling 389-ds-base
  • Downstream Linux distributions packaging 389-ds-base

Discovery Timeline

  • 2026-08-25 - CVE-2026-78701 published to NVD
  • 2026-08-25 - Last updated in NVD database

Technical Details for CVE-2026-78701

Vulnerability Analysis

The flaw resides in the SASL UNBIND handling path within 389-ds-base. LDAP clients that authenticate through SASL issue an UNBIND operation to terminate the session and release server-side resources. A specially crafted UNBIND request prevents the server from cleanly completing this teardown, leaving the connection in a stalled state.

Stalled connections retain memory, file descriptors, and worker thread context. An authenticated attacker can iterate the pattern across many connections until the server can no longer service legitimate clients. Because the attack is triggered post-authentication, standard network filtering does not block it; the attacker only needs valid directory credentials.

The issue is categorized under [CWE-787] in the NVD record, though the observable behavior aligns with a resource exhaustion condition in the SASL cleanup logic. Refer to the Red Hat CVE-2026-78701 Advisory for vendor analysis.

Root Cause

The root cause is improper handling of malformed input during SASL UNBIND processing. The server fails to release connection state when the request deviates from expected structure, leaving resources allocated indefinitely.

Attack Vector

An attacker authenticates to the LDAP server using any valid credentials, including low-privilege bind accounts. The attacker then transmits crafted SASL UNBIND messages over the network. Each malformed request consumes a connection slot without releasing it. Sustained abuse depletes server capacity and produces a denial-of-service condition for directory-dependent applications such as authentication, mail routing, and identity federation.

No verified public exploit code is available at this time. See the Red Hat Bug Report #2523232 for reproduction context.

Detection Methods for CVE-2026-78701

Indicators of Compromise

  • Growing count of open LDAP connections that never issue subsequent operations after a SASL bind sequence.
  • Rising memory and file descriptor usage on the ns-slapd process without a corresponding increase in successful operations.
  • LDAP client timeouts and bind failures reported by dependent services during periods of normal query volume.

Detection Strategies

  • Correlate SASL bind events with UNBIND completion events in 389-ds-base access logs; unmatched pairs from the same source warrant investigation.
  • Alert on sustained increases in the currentconnections metric exposed by the cn=monitor entry when total operations remain flat.
  • Baseline per-account connection counts and flag identities that hold unusually high concurrent sessions.

Monitoring Recommendations

  • Ship 389-ds-base access and error logs to a centralized analytics platform for long-window correlation.
  • Track process-level resource metrics (RSS, open files, thread count) for ns-slapd and alert on trend deviations.
  • Monitor authenticated client IP ranges for repeated bind cycles that fail to terminate cleanly.

How to Mitigate CVE-2026-78701

Immediate Actions Required

  • Apply vendor updates for 389-ds-base as soon as fixed packages are published by your Linux distribution.
  • Audit LDAP bind accounts and remove or rotate credentials that are unused, shared, or overly permissioned.
  • Restrict LDAP network exposure so that only trusted application tiers can reach the directory service.

Patch Information

Consult the Red Hat CVE-2026-78701 Advisory for fixed package versions and applicable errata. Track the Red Hat Bug Report #2523232 for upstream fix status in 389-ds-base. Downstream distributions that ship 389-ds-base should be checked for their own security advisories before production rollout.

Workarounds

  • Enforce per-client connection limits using the nsslapd-maxdescriptors and nsslapd-conntablesize server configuration parameters to cap resource consumption.
  • Configure idle timeout with nsslapd-idletimeout to forcibly reap stalled connections after a defined interval.
  • Place directory servers behind an authenticating load balancer or firewall policy that limits concurrent sessions per source address.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.