CVE-2026-18922: 389-ds-base: 389-ds-base: sasl plain authentication allows privilege escalation to directory manager via stale identity in cyrus sasl auxiliary property
- Is it exploited?
Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.
- How likely is exploitation in the next 30 days?
- 0.6%
EPSS score, percentile 46.6 of all scored records. A probability estimated by FIRST, not a report of exploitation.
- How severe?
- 9.8 Critical
CVSS v3.1 base score, given by the CNA
- What should I do?
CISA has set no required action, because the vulnerability is not in KEV.
- Which versions are affected?
Unaffected 8060020260908152739.0ca98e7e; 8080020260903102346.f969626e; 8100020260904171440.37ed7c03; 9020020260903155914.1674d574; 9040020260903102623.1674d574; 0:3.2.0-10.el10_2; and 14 more
Source: CISA KEV 2026.10.29, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.
What to do
Workaround (from the CVE record)
Administrators can restrict nsslapd-allowed-sasl-mechanisms to only the mechanisms actually required (e.g. GSSAPI, EXTERNAL, GSS-SPNEGO), excluding PLAIN. Since the exploit chain requires the first bind attempt to be a failed SASL PLAIN bind as cn=Directory Manager, removing PLAIN from the allowed mechanism list prevents that step entirely — this blocks both the originally reported variant (valid low-privileged account) and the zero-credential SASL ANONYMOUS variant, since both depend on the same initial PLAIN bind to plant the stale identity.
Advisories and patches
- RHSA-2026:64771
- RHSA-2026:64776
- RHSA-2026:64778
- RHSA-2026:64779
- RHSA-2026:64780
- RHSA-2026:64781
- RHSA-2026:64783
- RHSA-2026:64784
- RHSA-2026:64785
- RHSA-2026:64789
- RHSA-2026:64790
- RHSA-2026:64791
This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.
Affected products and versions
As listed in the CVE record.
| Status | Versions |
|---|---|
| Unaffected | 8060020260908152739.0ca98e7e |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8080020260903102346.f969626e |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8100020260904171440.37ed7c03 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 9020020260903155914.1674d574 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 9040020260903102623.1674d574 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:3.2.0-10.el10_2 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:3.0.6-21.el10_0 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:1.2.11.15-97.el6_10.1 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:1.3.11.1-15.el7_9 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8100020260904155442.25e700aa |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8040020260901171549.96015a92 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8040020260901171549.96015a92 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8060020260901145727.824efc52 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8060020260901145727.824efc52 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8080020260831180218.6dbb3803 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 8080020260831180218.6dbb3803 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:2.8.0-10.el9_8 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:2.2.4-22.el9_2 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:2.4.5-29.el9_4 |
Versions not listed are: affected.
| Status | Versions |
|---|---|
| Unaffected | 0:2.6.1-24.el9_6 |
Versions not listed are: affected.
Versions the record lists as unaffected: 8060020260908152739.0ca98e7e, 8080020260903102346.f969626e, 8100020260904171440.37ed7c03, 9020020260903155914.1674d574, 9040020260903102623.1674d574, 0:3.2.0-10.el10_2, 0:3.0.6-21.el10_0, 0:1.2.11.15-97.el6_10.1.
Source: CVE List, as of . About the data.
About this vulnerability
A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect pa…
Summary: CVE record, as of .
- CISA has not added CVE-2026-18922 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
- The CVE record was published on 7 Sep 2026.
- The CVE record carries a CVSS v3.1 base score of 9.8 (Critical), given by its CNA.
- FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.6% (percentile 46.6), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
- CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact total.
- The credits in the CVE record name OpenAI as finder.
Source: CISA KEV 2026.10.29, as of ; CVE List, as of ; FIRST EPSS, as of . About the data.
Description
389-ds-base: 389-ds-base: sasl plain authentication allows privilege escalation to directory manager via stale identity in cyrus sasl auxiliary property
A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.
Source: CVE List, as of . About the data.
Weakness
CWE-287
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.
Timeline
| Date | Event |
|---|---|
| CVE record published | |
| CVE record last updated |
Known exploited Red Hat vulnerabilities
- CVE-2015-3246: Red Hat Libuser Race Condition Vulnerability
- CVE-2015-5287: Red Hat Automatic Bug Reporting Tool Privilege Escalation Vulnerability
- CVE-2018-14667: Red Hat JBoss RichFaces Framework Expression Language Injection Vulnerability
- CVE-2021-3560: Red Hat Polkit Incorrect Authorization Vulnerability
- CVE-2021-4034: Red Hat Polkit Out-of-Bounds Read and Write Vulnerability