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.
Affected products
redhat: directory server; redhat: 389 directory server; redhat: enterprise linux
References2
- access.redhat.com/security/cve/CVE-2026-18651 Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2510617 Issue TrackingVendor Advisory
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 21 · as of 13 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.