Skip to main content
VulnerabilityPublished Updated

CVE-2026-86345: Red Hat Directory Server 11 · Improper Restriction of Communication Channel to Intended Endpoints

Affects Red Hat Directory Server 11Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.19.0
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Directory Server 11389-ds-baseAffected–Fixed in–
Red Hat Directory Server 11redhat-ds:11/389-ds-baseAffected–Fixed in–
Red Hat Directory Server 12389-ds-baseAffected–Fixed in–
Red Hat Directory Server 12redhat-ds:12/389-ds-baseAffected–Fixed in–
Red Hat Directory Server 13389-ds-baseAffected–Fixed in–
Red Hat Enterprise Linux 10389-ds-baseAffected–Fixed in–

AI-suggested

Red Hat advises disabling StartTLS on port 389 and requiring ldaps:// (port 636) instead, as this protocol does not have a cleartext prefix vulnerable to injection. No configuration-only mitigation fully addresses the issue while StartTLS remains enabled on port 389. Users should follow the vendor advisory for updates and consider this mitigation until an official fix is available.

Description

A vulnerability in 389-ds-base allows an on-path attacker to inject crafted LDAP messages during StartTLS negotiation, causing a client to treat a failed authentication as successful. This occurs because the server does not discard plaintext bytes buffered before TLS upgrade, leading to message ID collisions. The flaw affects downstream client applications relying on LDAP bind results, not the server itself. Exploitation requires an active man-in-the-middle position and precise timing. Mitigation involves disabling StartTLS on port 389 and using ldaps:// on port 636 instead.

References

Community reviews

Loading reviews…