CVE-2026-11610
What it is
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. The vulnerable code path has existed since approximately 2013 (389-ds-base 1.3.2) and was not addressed by the CVE-2025-14905 fix, which patched a separate heap overflow in schema.c only.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-122
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-11610.md and follow it. Check whether this project is affected by CVE-2026-11610. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://access.redhat.com/errata/RHSA-2026:36195
- https://access.redhat.com/errata/RHSA-2026:36196
- https://access.redhat.com/errata/RHSA-2026:36197
- https://access.redhat.com/errata/RHSA-2026:36198
- https://access.redhat.com/errata/RHSA-2026:36200
- https://access.redhat.com/errata/RHSA-2026:36201
- https://access.redhat.com/errata/RHSA-2026:36202
- https://access.redhat.com/errata/RHSA-2026:36204
- https://access.redhat.com/errata/RHSA-2026:36205
- https://access.redhat.com/errata/RHSA-2026:36206
- https://access.redhat.com/errata/RHSA-2026:36208
- https://access.redhat.com/errata/RHSA-2026:36209
- https://access.redhat.com/errata/RHSA-2026:36585
- https://access.redhat.com/errata/RHSA-2026:36641
- https://access.redhat.com/errata/RHSA-2026:36660
- https://access.redhat.com/errata/RHSA-2026:36670
- https://access.redhat.com/errata/RHSA-2026:36671
- https://access.redhat.com/security/cve/CVE-2026-11610
- https://bugzilla.redhat.com/show_bug.cgi?id=2484414