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.
Published: 2026-08-03
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

During SASL PLAIN authentication, the server installs the connection credentials before checking if the account is administratively locked. If a bind attempt succeeds, the server reports failure to the client when the account lock is discovered, yet the authenticated state on the connection is left unchanged. The adversary can use the same connection with the locked account’s privileges, effectively bypassing the lock that should have revoked that account’s access. This flaw, a manifestation of CWE‑287, allows a valid user to retain unauthorized access to resources even after the account has been locked.

Affected Systems

Red Hat Directory Server versions 11, 12 and 13 as well as the Red Hat Enterprise Linux distributions 6 through 10 are affected. No additional version qualifiers were provided, so the entire scope of these products may be impacted.

Risk and Exploitability

The vulnerability’s CVSS score of 5.4 indicates moderate severity; the EPSS score is not available and the flaw is not listed in CISA’s KEV catalog. The likely attack vector is a remote LDAP client that can authenticate using SASL PLAIN with an account that has been locked. The attacker must already possess valid credentials for the locked account; once credentials are known, the flaw enables the attacker to maintain privileged access through the existing connection, circumventing the intended lockout. Because the authentication bypass occurs during normal protocol operation, exploitation requires only network visibility and knowledge of the account credentials.

Generated by OpenCVE AI on August 4, 2026 at 10:12 UTC.

Remediation

Vendor Workaround

When locking an account, also rotate its LDAP password. Locking the account alone is not enough: this flaw lets a bind with the account's still-valid password succeed even after it's locked.


OpenCVE Recommended Actions

  • Rotate the LDAP password of the account when it is locked to invalidate any cached credentials.
  • Apply any vendor‑supplied patches that address the SASL PLAIN authentication flaw.
  • Disallow or restrict SASL PLAIN authentication and enforce additional lock checks after the bind completes.

Generated by OpenCVE AI on August 4, 2026 at 10:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 10:45:00 +0000

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat enterprise Linux
Redhat redhat Directory Server
Vendors & Products Red Hat
Red Hat enterprise Linux
Redhat redhat Directory Server

Tue, 04 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 03 Aug 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 03 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
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.
Title 389-ds-base: 389-ds-base: sasl plain bind installs connection credentials before account-lock check, allowing continued access as a locked account
First Time appeared Redhat
Redhat directory Server
Redhat enterprise Linux
Weaknesses CWE-287
CPEs cpe:/a:redhat:directory_server:11
cpe:/a:redhat:directory_server:12
cpe:/a:redhat:directory_server:13
cpe:/o:redhat:enterprise_linux:10
cpe:/o:redhat:enterprise_linux:6
cpe:/o:redhat:enterprise_linux:7
cpe:/o:redhat:enterprise_linux:8
cpe:/o:redhat:enterprise_linux:9
Vendors & Products Redhat
Redhat directory Server
Redhat enterprise Linux
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

Red Hat Enterprise Linux
Redhat 389 Directory Server Directory Server Enterprise Linux Redhat Directory Server
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-08-03T16:58:47.716Z

Reserved: 2026-08-03T11:47:54.931Z

Link: CVE-2026-18651

cve-icon Vulnrichment

Updated: 2026-08-03T16:58:43.833Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-03T16:16:29.073

Modified: 2026-08-09T13:54:50.200

Link: CVE-2026-18651

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-03T00:00:00Z

Links: CVE-2026-18651 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T10:22:13Z

Weaknesses