CVE-2026-11774: 389-ds-base: 389-ds-base: integer overflow in sasl packet length bypasses size limit leading to heap buffer overflow
An integer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasl_io_start_packet(), adding sizeof(uint32_t) to a crafted SASL packet length prefix of 0xFFFFFFFC causes unsigned wraparound to zero, bypassing the nsslapd-maxsasliosize limit and leading to a heap buffer overflow of up to approximately 2 megabytes of attacker-controlled data. After a successful SASL bind with integrity protection (SSF > 0), a remote attacker can cause a Denial of Service (DoS) or achieve Remote Code Execution (RCE). In FreeIPA and Red Hat Identity Management deployments, any domain user with a valid Kerberos ticket, enrolled host, or service account can trigger this vulnerability over the network. This flaw is independent of CVE-2025-14905, which patched schema.c only and did not modify sasl_io.c.
Security readout for executives and security teams
Plain-English summary
CVE-2026-11774 affects 389 Directory Server in Red Hat Directory Server, RHEL, FreeIPA, and Red Hat Identity Management contexts. A logged-in domain user or service account can send malformed SASL traffic after authentication, potentially crashing the directory service or enabling code execution.
Executive priority
Treat as a high-priority identity infrastructure issue. The vulnerability can affect core directory services, may be reachable by low-privileged authenticated principals, and carries denial-of-service plus possible remote code execution impact.
Technical view
The flaw is an integer overflow in sasl_io_start_packet(). A crafted SASL packet length can wrap when sizeof(uint32_t) is added, bypass nsslapd-maxsasliosize, and trigger a heap buffer overflow after a successful SASL bind with SSF greater than zero.
Likely exposure
Exposure is most likely in Red Hat 389-ds-base/redhat-ds deployments, including listed RHEL 7 ELS, RHEL 8, RHEL 9, RHEL 10, and Red Hat Directory Server streams. FreeIPA and Red Hat IdM environments are notable because ordinary domain credentials may be sufficient.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. Exploitation requires network access plus a successful SASL bind with integrity protection, so this is not unauthenticated, but domain users, enrolled hosts, or service accounts may qualify.
Researcher notes
This is distinct from CVE-2025-14905; the source states that earlier fix changed schema.c only, not sasl_io.c. Focus review on SASL I/O length handling and authenticated SASL sessions with SSF greater than zero.
Mitigation direction
Identify all 389-ds-base and redhat-ds deployments in affected Red Hat streams.
Apply the relevant Red Hat RHSA updates for each product stream.
Check Red Hat CVE guidance for exact fixed packages and any stream-specific instructions.
Prioritize FreeIPA and Red Hat IdM servers reachable by domain users or service accounts.
Restrict directory service exposure while patching, where operationally feasible.
Validation and detection
Compare installed 389-ds-base or redhat-ds versions with affected versions in Red Hat advisories.
Confirm each server has received the matching RHSA update for its RHEL or Directory Server stream.
Inventory FreeIPA and Red Hat IdM systems using Kerberos-backed SASL authentication.
Review directory service availability logs for unexplained crashes or restarts.
Verify nsslapd-maxsasliosize is not treated as sufficient protection for this flaw.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.