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.
Metrics
CVSS 3.1 5.4/10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat Directory Server 11 | — |
| Red Hat | Red Hat Directory Server 12 | — |
| Red Hat | Red Hat Directory Server 13 | — |
| Red Hat | Red Hat Enterprise Linux 10 | — |
| Red Hat | Red Hat Enterprise Linux 6 | — |
| Red Hat | Red Hat Enterprise Linux 7 | — |
| Red Hat | Red Hat Enterprise Linux 8 | — |
| Red Hat | Red Hat Enterprise Linux 9 | — |
References
- https://access.redhat.com/security/cve/CVE-2026-18651Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2510617Issue Tracking, Vendor Advisory
Timeline
- Published
- Aug 3, 2026
- Last modified
- Nov 5, 2026
- NVD status
- Analyzed