Medium · CVSS 6.5CVE-2026-78701

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

Answer in brief

CVE-2026-78701 records a Medium severity (CVSS 6.5) vulnerability in 389-ds-base: 389-ds-base: cve-2026-11610 incomplete fix may introduce a connection-stall dos. The current sources do not mark it as known exploited. The current feed maps Red Hat/389-ds:1.4/389-ds-base (generic), Red Hat/389-ds-base (generic), Red Hat/redhat-ds:11/389-ds-base (generic), Red Hat/redhat-ds:12/389-ds-base (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 25, 2026Updated Oct 8, 2026Source checked Oct 10, 2026First seen by HOL Aug 25, 2026Material review Oct 8, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 4 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/389-ds:1.4/389-ds-base (generic), Red Hat/389-ds-base (generic), Red Hat/redhat-ds:11/389-ds-base (generic), Red Hat/redhat-ds:12/389-ds-base (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Red Hat/389-ds:1.4/389-ds-basegeneric	*	Not reported
Red Hat/389-ds-basegeneric	*	Not reported
Red Hat/redhat-ds:11/389-ds-basegeneric	*	Not reported
Red Hat/redhat-ds:12/389-ds-basegeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/389-ds:1.4/389-ds-base, Red Hat/389-ds-base, Red Hat/redhat-ds:11/389-ds-base.
Review the reported fix. Source-reported workaround: To mitigate this issue, restrict network access to the 389-ds-base service to only trusted clients and networks. This can be achieved by configuring firewall rules to limit inbound connections to the LDAP ports (typically 389 for LDAP and 636 for LDAPS) to known, authorized IP addresses or subnets. Example using `firewalld`: ```bash # firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_IP_OR_SUBNET>" port port="389" protocol="tcp" accept' # firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_IP_OR_SUBNET>" port port="636" protocol="tcp" accept' # firewall-cmd --reload ``` Replace `<TRUSTED_IP_OR_SUBNET>` with the actual IP addresses or network ranges of your trusted clients. This action may impact legitimate clients if not configured correctly. A service restart is not required for firewall changes to take effect.

Evidence timeline and material changes

Published upstream
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 25, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.