PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-18922 Red Hat CVE debrief

A flaw in 389 Directory Server allows an attacker to gain Directory Manager authority without valid credentials by exploiting the SASL PLAIN authentication mechanism. This is achieved by sending a SASL PLAIN bind with an incorrect password, followed by a SASL ANONYMOUS bind on the same connection. A variant using a valid low-privileged account's own successful bind is also possible. The CVSS score is 9.8, indicating critical severity.

Vendor
Red Hat
Product
Red Hat Directory Server 11
CVSS
CRITICAL 9.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-07
Original CVE updated
2026-09-07
Advisory published
2026-09-07
Advisory updated
2026-09-07

Who should care

Administrators and security teams responsible for 389 Directory Server deployments, particularly those using SASL PLAIN authentication, should assess exposure and implement additional security measures.

Why it matters

CVE-2026-18922 is a critical vulnerability in 389 Directory Server that allows attackers to gain Directory Manager authority without valid credentials. Defenders should prioritize authentication and authorization mechanisms, implement additional security measures, and monitor for potential exploitation attempts. The impact of this vulnerability requires verification from official sources, and the need for remediation is high.

  • Potential unauthorized access to sensitive data
  • Elevation of privileges for attackers
  • Compromise of directory server integrity
  • Need for verification of affected versions and remediation

Technical summary

The flaw in 389 Directory Server allows an attacker to install a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt on a connection following a subsequent, unrelated successful bind. This can be exploited to gain Directory Manager authority without valid credentials. The vulnerability affects deployments using SASL PLAIN authentication and can be mitigated by reviewing and updating authentication and authorization mechanisms. A successful exploit could result in elevation of privileges and compromise of directory server integrity.

Defensive priority

High priority for authentication and authorization mechanisms

Recommended defensive actions

  • Review and update authentication and authorization mechanisms
  • Implement additional security measures for SASL PLAIN authentication
  • Monitor for potential exploitation attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD vulnerability detail provide information on the flaw and its potential impact. Red Hat has also provided a reference for the vulnerability. Defenders should verify affected versions and assess exposure. The evidence is limited, and further verification is needed to determine the full scope of the vulnerability. Official sources indicate a critical severity score of 9.8. The flaw affects 389 Directory Server deployments using SASL PLAIN authentication.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-18922 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-18922

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-18922 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-18922

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.