High [CVE-2026-11610] Heap buffer overflow in sasl_io_recv via padded SASL UNBIND
This high-severity Red Hat Linux advisory covers CVE-2026-11610 affecting Red Hat Directory Server 11.5 E4S for RHEL 8, Red Hat Directory Server 11.7 E4S for RHEL 8, Red Hat Directory Server 11.9 for RHEL 8.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). After a successful SASL bind with integrity protection (SSF > 0), an authenticated attacker can send a specially crafted oversized LDAP UNBIND packet that is copied into a 512-byte heap receive buffer without a bounds check in sasl_io_recv() in sasl_io.c.
This allows up to approximately 2 megabytes of attacker-controlled data to overflow the buffer, causing a denial of service (server crash).
In FreeIPA and Red Hat Identity Management deployments, any domain user with a valid Kerberos ticket, any enrolled host, or any service account can trigger this vulnerability over the network after authenticating via GSSAPI. Red Hat rates this issue as Important impact.
Exploitation requires a valid SASL-authenticated LDAP session, not Directory Manager access. Any user who can bind with SASL mechanisms such as GSSAPI/Kerberos or DIGEST-MD5 can trigger the denial of service.
In deployments where domain users, enrolled hosts, and service accounts routinely authenticate to the directory over Kerberos, the attack surface includes any such principal with network access to LDAP. This flaw is independent of CVE-2025-14905, which patched a separate heap overflow in schema.c and did not modify sasl_io.c.
Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
- 1.3.2
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- redhat-ds:11-8060020260702180044.0ca98e7e
- redhat-ds:11-8080020260702180836.f969626e
- redhat-ds:11-8100020260702145313.37ed7c03
- redhat-ds:12-9020020260703060155.1674d574
- redhat-ds:12-9040020260703055735.1674d574
- 389-ds-base-0:3.2.0-8.el10_2
- 389-ds-base-0:3.0.6-19.el10_0
- 389-ds-base-0:1.3.11.1-13.el7_9
- 389-ds:1.4-8100020260626120929.25e700aa
- 389-ds:1.4-8040020260629123121.96015a92
- 389-ds:1.4-8060020260626130540.824efc52
- 389-ds:1.4-8080020260630025241.6dbb3803
- 389-ds-base-0:2.8.0-8.el9_8
- 389-ds-base-0:2.2.4-19.el9_2
- 389-ds-base-0:2.4.5-26.el9_4
- 389-ds-base-0:2.6.1-22.el9_6
- dirsrv/dirsrv-container-rhel10:1783452100
- RHSA-2026:36204
- RHSA-2026:36208
- RHSA-2026:36200
- RHSA-2026:36641
- RHSA-2026:36209
- RHSA-2026:36196
- RHSA-2026:36670
- RHSA-2026:36205
- RHSA-2026:36201
- RHSA-2026:36206
- RHSA-2026:36202
- RHSA-2026:36197
- RHSA-2026:36195
- RHSA-2026:36585
- RHSA-2026:36198
- RHSA-2026:36671
- RHSA-2026:36660
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- There is no complete workaround for this flaw. Mitigations that reduce exposure: 1. Restrict network access to LDAP ports (389/636) to trusted networks only. Note: In FreeIPA/IdM deployments, enrolled clients require LDAP access and this may not be practical. 2. If DIGEST-MD5 is not required, disable it via nsslapd-allowed-sasl-mechanisms in cn=config. GSSAPI/Kerberos cannot be disabled in FreeIPA/IdM without breaking domain authentication. 3. Monitor for oversized LDAP UNBIND packets (standard UNBIND is 7 bytes; alert on UNBIND packets exceeding ~100 bytes). 4. Lowering nsslapd-maxbersize reduces maximum overflow size but does not eliminate the vulnerability.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.