PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-18922 Red Hat CVE debrief

A critical vulnerability was found in Red Hat Directory Server 11, allowing an attacker to gain Directory Manager authority without valid credentials through a SASL PLAIN authentication flaw. This issue arises from a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt, which can be installed on a connection following a subsequent, unrelated successful bind.

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-10-08
Advisory published
2026-09-07
Advisory updated
2026-10-08

Who should care

Administrators of Red Hat Directory Server 11, especially those responsible for authentication and directory server management, should assess exposure and apply patches or mitigations as necessary.

Why it matters

CVE-2026-18922 is a critical vulnerability in Red Hat Directory Server 11 that allows an attacker to gain Directory Manager authority without valid credentials. This issue requires immediate attention from administrators responsible for authentication and directory server management to assess exposure and apply patches or mitigations.

  • Potential unauthorized access to directory server
  • Possible elevation of privileges
  • Required verification of authentication mechanisms
  • Necessity for patch application or mitigation

Technical summary

The vulnerability is caused by a flaw in the SASL PLAIN authentication mechanism of Red Hat Directory Server 11. An attacker can exploit this by sending a SASL PLAIN bind with an incorrect password, then completing a SASL ANONYMOUS bind on the same connection, effectively granting Directory Manager authority without valid credentials. This issue requires immediate attention from administrators responsible for authentication and directory server management to assess exposure and apply patches or mitigations. The affected product deployments should be verified, and owners should be assigned for follow-up.

Defensive priority

High priority for authentication and directory server administrators to verify and apply patches

Recommended defensive actions

  • Verify and apply patches from Red Hat
  • Review authentication logs for potential exploitation attempts
  • Implement additional monitoring for directory server activity
  • 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.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The vulnerability was reported by an unknown source and confirmed by Red Hat. The NVD entry is currently 9.8 CRITICAL. This issue arises from a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt, which can be installed on a connection following a subsequent, unrelated successful bind. To verify, defenders should review authentication logs and check for potential exploitation attempts. Red Hat has provided patches for this issue, which should be applied as soon as possible. Additional monitoring,

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.