CVE-2026-18651: A flaw was found in 389 Directory Server. During SASL PLAIN authentication, the server installs connection-level bind…
CVE-2026-18651 · Severity: medium · CVSS 5.4 · Published 2026-08-03
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-18651 being exploited in the wild.
How severe is CVE-2026-18651?
Medium severity, with a CVSS score of 5.4, published 3 August 2026.
Which products and versions are affected?
Redhat 389 Directory Server, Redhat Directory Server, Redhat Enterprise Linux. The advisory does not name versions.
Is there a fix for CVE-2026-18651?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-18651?
Check whether you run Redhat 389 Directory Server, Redhat Directory Server or Redhat Enterprise Linux. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.