CVE-2026-11610

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-07. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
Patch available. Sources: redhat.
redhat

2484414 – (CVE-2026-11610) CVE-2026-11610 389-ds-base: 389-ds-base: Heap buffer overflow in sasl_io_recv() via padded SASL UNBIND

https://bugzilla.redhat.com/show_bug.cgi?id=2484414
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-11610

Vendor Advisories for CVE-2026-11610(18)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhat389-ds-base-0:2.2.4-19.el9_22026-07-08redhat
redhatredhat-ds:12-9020020260703060155.1674d5742026-07-08redhat
redhat389-ds-base-0:2.6.1-22.el9_62026-07-08redhat
redhatdirsrv/dirsrv-container-rhel10:17834521002026-07-08redhat
redhat389-ds-base-0:3.0.6-19.el10_02026-07-08redhat
redhatredhat-ds:11-8100020260702145313.37ed7c032026-07-07redhat
redhatredhat-ds:12-9040020260703055735.1674d5742026-07-07redhat
redhat389-ds-base-0:1.3.11.1-13.el7_92026-07-07redhat
redhatredhat-ds:11-8060020260702180044.0ca98e7e2026-07-07redhat
redhat389-ds:1.4-8040020260629123121.96015a922026-07-07redhat
redhat389-ds:1.4-8060020260626130540.824efc522026-07-07redhat
redhat389-ds:1.4-8080020260630025241.6dbb38032026-07-07redhat
redhat389-ds:1.4-8100020260626120929.25e700aa2026-07-07redhat
redhat389-ds-base-0:3.2.0-8.el10_22026-07-07redhat
redhat389-ds-base-0:2.8.0-8.el9_82026-07-07redhat
redhat389-ds-base-0:2.4.5-26.el9_42026-07-07redhat
redhatredhat-ds:11-8080020260702180836.f969626e2026-07-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 78× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-29 05:59 UTCVendor advisory
  2. 2026-07-29 05:59 UTCGHSA enrichment
  3. 2026-07-28 17:17 UTCEG score recompute
  4. 2026-07-28 17:17 UTCVendor advisory
  5. 2026-07-28 17:17 UTCGHSA enrichment
  6. 2026-07-28 15:36 UTCEPSS rescore
  7. 2026-07-28 04:26 UTCVendor advisory
  8. 2026-07-28 04:26 UTCGHSA enrichment
  9. 2026-07-27 15:43 UTCEG score recompute
  10. 2026-07-27 15:43 UTCVendor advisory
  11. 2026-07-27 15:43 UTCGHSA enrichment
  12. 2026-07-27 14:13 UTCEPSS rescore
  13. 2026-07-27 01:24 UTCEG score recompute
  14. 2026-07-27 01:24 UTCVendor advisory
  15. 2026-07-27 01:24 UTCGHSA enrichment
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 12:42 UTCEG score recompute
  19. 2026-07-26 12:42 UTCVendor advisory
  20. 2026-07-26 12:42 UTCGHSA enrichment
  21. 2026-07-25 14:17 UTCEPSS rescore
  22. 2026-07-24 14:17 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:04 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
Show 53 more
  1. 2026-07-21 15:24 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:30 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 22:24 UTCVendor advisory
  7. 2026-07-16 22:24 UTCGHSA enrichment
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 09:43 UTCVendor advisory
  10. 2026-07-16 09:43 UTCGHSA enrichment
  11. 2026-07-15 21:02 UTCVendor advisory
  12. 2026-07-15 21:02 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 08:21 UTCVendor advisory
  15. 2026-07-15 08:20 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 19:40 UTCVendor advisory
  18. 2026-07-14 19:40 UTCGHSA enrichment
  19. 2026-07-14 07:01 UTCVendor advisory
  20. 2026-07-14 07:00 UTCGHSA enrichment
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 18:20 UTCVendor advisory
  23. 2026-07-13 18:20 UTCGHSA enrichment
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-13 05:37 UTCVendor advisory
  26. 2026-07-13 05:37 UTCGHSA enrichment
  27. 2026-07-12 16:57 UTCVendor advisory
  28. 2026-07-12 16:57 UTCGHSA enrichment
  29. 2026-07-12 05:46 UTCEPSS rescore
  30. 2026-07-12 04:15 UTCVendor advisory
  31. 2026-07-12 04:15 UTCGHSA enrichment
  32. 2026-07-11 15:35 UTCVendor advisory
  33. 2026-07-11 15:35 UTCGHSA enrichment
  34. 2026-07-11 08:27 UTCEPSS rescore
  35. 2026-07-11 02:55 UTCVendor advisory
  36. 2026-07-11 02:55 UTCGHSA enrichment
  37. 2026-07-10 14:15 UTCVendor advisory
  38. 2026-07-10 14:15 UTCGHSA enrichment
  39. 2026-07-10 01:34 UTCVendor advisory
  40. 2026-07-10 01:34 UTCGHSA enrichment
  41. 2026-07-09 19:10 UTCEPSS rescore
  42. 2026-07-09 12:52 UTCVendor advisory
  43. 2026-07-09 12:52 UTCGHSA enrichment
  44. 2026-07-09 00:08 UTCVendor advisory
  45. 2026-07-09 00:07 UTCGHSA enrichment
  46. 2026-07-08 15:15 UTCEPSS rescore
  47. 2026-07-08 15:15 UTCEPSS rescore
  48. 2026-07-08 11:27 UTCVendor advisory
  49. 2026-07-08 11:26 UTCGHSA enrichment
  50. 2026-07-07 22:46 UTCGHSA enrichment
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-07 10:07 UTCEG score recompute
  53. 2026-07-07 10:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-11610?
CVE-2026-11610 is a high vulnerability published on July 7, 2026. 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…
When was CVE-2026-11610 disclosed?
CVE-2026-11610 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11610 actively exploited?
CVE-2026-11610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.6% of all scored CVEs.
What is the CVSS score of CVE-2026-11610?
CVE-2026-11610 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-11610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11610, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11610

Explore →

Is Your Infrastructure Affected by CVE-2026-11610?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs