CVE-2026-18663: Double Free in Red Hat Red Hat Directory Server 11
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function frees the parsed controls array on the Session Tracking critical-control rejection path without clearing the SLAPI_REQCONTROLS pblock slot. Operation teardown then frees the same pointer again, causing a double-free. An unauthenticated remote attacker can trigger this with a single BIND request carrying a critical Session Tracking control, resulting in heap corruption and potential denial of service.
AI Analysis
Technical Summary
A double-free vulnerability exists in the get_ldapmessage_controls_ext() function of 389-ds-base, part of Red Hat Directory Server 11. The function frees a parsed controls array on the Session Tracking critical-control rejection path without clearing the associated SLAPI_REQCONTROLS pblock slot, causing a second free during operation teardown. An unauthenticated remote attacker can trigger this via a single BIND request with a critical Session Tracking control, resulting in heap corruption and potential denial of service. Red Hat rates this as moderate severity due to the requirement of a critical Session Tracking control in the request and because RHEL 10 and RHDS 13 builds using jemalloc do not crash. The vulnerability affects only 389-ds-base 3.x versions that include the Session Tracking control feature. Mitigation includes configuring the server to ignore the criticality flag of this control or restricting LDAP port access. No evidence of information disclosure or privilege escalation is reported.
Potential Impact
The vulnerability can cause heap corruption leading to denial of service by crashing the ns-slapd process when exploited on builds using the glibc allocator. Builds using jemalloc (such as RHEL 10 and RHDS 13) absorb the double-free without crashing, limiting impact. There is no demonstrated information disclosure or privilege escalation. Exploitation requires sending an unauthenticated BIND request with a critical Session Tracking control. The impact is therefore limited to availability disruption on certain builds.
Mitigation Recommendations
Red Hat has not indicated an official patch release yet; patch status is not confirmed—check the vendor advisory for updates. Administrators can mitigate the issue by adding the Session Tracking control OID (1.3.6.1.4.1.21008.108.63.1) to the ds-ignored-control-criticality configuration attribute to ignore the criticality flag and prevent the vulnerable code path. Additionally, restricting network access to LDAP ports (389/636) to trusted clients reduces exposure. These mitigations reduce the risk until an official fix is available.
CVE-2026-18663: Double Free in Red Hat Red Hat Directory Server 11
Description
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function frees the parsed controls array on the Session Tracking critical-control rejection path without clearing the SLAPI_REQCONTROLS pblock slot. Operation teardown then frees the same pointer again, causing a double-free. An unauthenticated remote attacker can trigger this with a single BIND request carrying a critical Session Tracking control, resulting in heap corruption and potential denial of service.
CVSS v3.1
Score 5.9medium
Affected software
Red Hat
Red Hat Directory Server 11
Red Hat
Red Hat Directory Server 12
Red Hat
Red Hat Directory Server 13
Red Hat
Red Hat Enterprise Linux 10
Red Hat
Red Hat Enterprise Linux 6
Red Hat
Red Hat Enterprise Linux 7
Red Hat
Red Hat Enterprise Linux 8
Red Hat
Red Hat Enterprise Linux 9
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
A double-free vulnerability exists in the get_ldapmessage_controls_ext() function of 389-ds-base, part of Red Hat Directory Server 11. The function frees a parsed controls array on the Session Tracking critical-control rejection path without clearing the associated SLAPI_REQCONTROLS pblock slot, causing a second free during operation teardown. An unauthenticated remote attacker can trigger this via a single BIND request with a critical Session Tracking control, resulting in heap corruption and potential denial of service. Red Hat rates this as moderate severity due to the requirement of a critical Session Tracking control in the request and because RHEL 10 and RHDS 13 builds using jemalloc do not crash. The vulnerability affects only 389-ds-base 3.x versions that include the Session Tracking control feature. Mitigation includes configuring the server to ignore the criticality flag of this control or restricting LDAP port access. No evidence of information disclosure or privilege escalation is reported.
Potential Impact
The vulnerability can cause heap corruption leading to denial of service by crashing the ns-slapd process when exploited on builds using the glibc allocator. Builds using jemalloc (such as RHEL 10 and RHDS 13) absorb the double-free without crashing, limiting impact. There is no demonstrated information disclosure or privilege escalation. Exploitation requires sending an unauthenticated BIND request with a critical Session Tracking control. The impact is therefore limited to availability disruption on certain builds.
Mitigation Recommendations
Red Hat has not indicated an official patch release yet; patch status is not confirmed—check the vendor advisory for updates. Administrators can mitigate the issue by adding the Session Tracking control OID (1.3.6.1.4.1.21008.108.63.1) to the ds-ignored-control-criticality configuration attribute to ignore the criticality flag and prevent the vulnerable code path. Additionally, restricting network access to LDAP ports (389/636) to trusted clients reduces exposure. These mitigations reduce the risk until an official fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-08-03T13:22:45.359Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-18663","vendor":"Red Hat"}]
Threat ID: 6a7c3fd8bf8831d53957e271
Added to database: 08/12/2026, 09:41:44 UTC
Last enriched: 08/12/2026, 10:00:17 UTC
Last updated: 09/26/2026, 13:47:43 UTC
Views: 64
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.