Skip to main content
VulnerabilityPublished

CVE-2026-18651: Red Hat Directory Server 11 · Improper Authentication

Affects Red Hat Directory Server 11Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-08-03.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Directory Server 11389-ds-baseAffected–Fixed in–
Red Hat Directory Server 12389-ds-baseAffected–Fixed in–
Red Hat Directory Server 13389-ds-baseAffected–Fixed in–
Red Hat Enterprise Linux 10389-ds-baseAffected–Fixed in–
Red Hat Enterprise Linux 6389-ds-baseAffected–Fixed in–
Red Hat Enterprise Linux 7389-ds-baseAffected–Fixed in–

Description

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, the server installs connection-level bind credentials before performing the account-lock check. If the account is subsequently found to be locked, the bind is reported as failed to the client, but the already-installed authenticated state on the connection is not reverted. A client that supplies valid credentials for an account that has been administratively locked can continue to use the same connection with that account's privileges, defeating account lock as an access-revocation control.

References

Community reviews

Loading reviews…