Home/CVE/A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server
(389-ds-base). After a successful SA
CVE
CVE-2026-11610
A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server
(389-ds-base). After a successful SA
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.
HIGH · CVSS 8.8
EPSS 0.00627
EPSS exploitation odds0.63% · top 54%
Schedule remediation
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-11610, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
↗
Exploitation momentum
3 days of EPSSrising
Exploitation pressure is rising. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
0.63%
Top 54%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Tech impact
total
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLifecycle
- 07 Jul 2026Published to NVD
- 08 Jul 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
1Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
CWE-122Heap-based Buffer Overflow
▤
Affected Packages
5Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
AlmaLinux:9
389-ds-base
fixed in 2.8.0-8.el9_8
AlmaLinux:9
389-ds-base-devel
fixed in 2.8.0-8.el9_8
AlmaLinux:9
389-ds-base-libs
fixed in 2.8.0-8.el9_8
AlmaLinux:9
389-ds-base-snmp
fixed in 2.8.0-8.el9_8
AlmaLinux:9
python3-lib389
fixed in 2.8.0-8.el9_8
▤
Related CVEs
4CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2006-10002
XML::Parser versions through 2.45 for Perl could overflow the pre-allocated buff...
same CWE-122
HIGH
CVE-2006-10003
XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflo...
same CWE-122
CRITICAL
CVE-2013-3245
plugins/demux/libmkv_plugin.dll in VideoLAN VLC Media Player 2.0.7, and possibly...
same CWE-122
MEDIUM
CVE-2013-7353
Integer overflow in the png_set_unknown_chunks function in libpng/pngset.c in li...
same CWE-122
MEDIUM
📦
Fixed versions by distribution
17The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle all389-ds-base fixed in 0:2.8.0-8.el9_8
oracle all389-ds-base-devel fixed in 0:2.8.0-8.el9_8
oracle all389-ds-base-legacy-tools fixed in 0:1.4.3.39-25.module+el8.10.0+90949+c5bfd23c
oracle all389-ds-base-libs fixed in 0:2.8.0-8.el9_8
oracle all389-ds-base-snmp open
oracle allpython3-lib389 fixed in 0:2.8.0-8.el9_8
rhel 8389-ds-base fixed in 0:1.4.3.39-25.module+el8.10.0+24462+1b66c107
rhel 8389-ds-base-devel open
rhel 8389-ds-base-legacy-tools open
rhel 8389-ds-base-libs open
rhel 8389-ds-base-snmp open
rhel 8python3-lib389 open
rhel 9389-ds-base open
rhel 9389-ds-base-devel open
rhel 9389-ds-base-libs open
rhel 9389-ds-base-snmp fixed in 0:2.8.0-8.el9_8
rhel 9python3-lib389 open
⚑
Vendor Advisories
17🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.