CVE-2026-11610

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-42026 (ENISA EUVD) · GHSA-2g8g-f92j-g4gq (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (2)

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

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
Red HatMentions a patch (unverified)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatredhat-ds:12-9020020260703060155.1674d5742026-07-08redhat
redhat389-ds-base-0:2.2.4-19.el9_22026-07-08redhat
redhat389-ds-base-0:2.6.1-22.el9_62026-07-08redhat
redhat389-ds-base-0:3.0.6-19.el10_02026-07-08redhat
redhatdirsrv/dirsrv-container-rhel10:17834521002026-07-08redhat
redhat389-ds:1.4-8080020260630025241.6dbb38032026-07-07redhat
redhat389-ds-base-0:2.8.0-8.el9_82026-07-07redhat
redhat389-ds-base-0:3.2.0-8.el10_22026-07-07redhat
redhat389-ds:1.4-8100020260626120929.25e700aa2026-07-07redhat
redhat389-ds:1.4-8040020260629123121.96015a922026-07-07redhat
redhat389-ds:1.4-8060020260626130540.824efc522026-07-07redhat
redhatredhat-ds:12-9040020260703055735.1674d5742026-07-07redhat
redhatredhat-ds:11-8100020260702145313.37ed7c032026-07-07redhat
redhatredhat-ds:11-8080020260702180836.f969626e2026-07-07redhat
redhat389-ds-base-0:1.3.11.1-13.el7_92026-07-07redhat
redhat389-ds-base-0:2.4.5-26.el9_42026-07-07redhat
redhatredhat-ds:11-8060020260702180044.0ca98e7e2026-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.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base1.4.4.11-2 ... 3.1.2+vendor1-2 (23 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base2.3.1+dfsg1-1 ... 3.3.1-3 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base3.1.2+dfsg1-1 ... 3.3.1-3 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 331 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 231 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-25 14:50 UTCEG score recompute
  5. 2026-10-25 05:15 UTCEG score recompute
  6. 2026-10-25 05:15 UTCVendor advisory
  7. 2026-10-25 05:15 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-18 05:05 UTCEG score recompute
  16. 2026-10-17 19:03 UTCEG score recompute
  17. 2026-10-17 19:03 UTCVendor advisory
  18. 2026-10-17 19:03 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-12 16:37 UTCEG score recompute
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-10-11 20:13 UTCEG score recompute
  2. 2026-10-11 18:25 UTCEG score recompute
  3. 2026-10-11 14:58 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-09-28 13:38 UTCEG score recompute
  18. 2026-09-28 13:38 UTCVendor advisory
  19. 2026-09-28 13:38 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-23 06:19 UTCEG score recompute
  23. 2026-09-23 06:19 UTCVendor advisory
  24. 2026-09-23 06:19 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-18 05:51 UTCEG score recompute
  28. 2026-09-18 05:51 UTCVendor advisory
  29. 2026-09-18 05:51 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-13 23:54 UTCEG score recompute
  32. 2026-09-13 23:54 UTCVendor advisory
  33. 2026-09-13 23:54 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  34. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-13 08:33 UTCVendor advisory
  36. 2026-09-13 08:33 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  37. 2026-09-12 16:45 UTCEG score recompute
  38. 2026-09-12 16:45 UTCVendor advisory
  39. 2026-09-12 16:45 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  41. 2026-09-12 03:45 UTCEG score recompute
  42. 2026-09-12 03:45 UTCVendor advisory
  43. 2026-09-12 03:45 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-09-06 14:08 UTCEG score recompute
  50. 2026-09-06 14:08 UTCVendor advisory
  51. 2026-09-06 14:08 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-09-05 22:54 UTCEG score recompute
  54. 2026-09-05 22:54 UTCVendor advisory
  55. 2026-09-05 22:54 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  57. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  58. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-08-30 20:23 UTCEG score recompute
  61. 2026-08-30 20:23 UTCVendor advisory
  62. 2026-08-30 20:23 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-30 07:44 UTCEG score recompute
  65. 2026-08-30 07:44 UTCVendor advisory
  66. 2026-08-30 07:44 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  69. 2026-08-27 21:56 UTCEG score recompute
  70. 2026-08-27 21:56 UTCVendor advisory
  71. 2026-08-27 21:56 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  73. 2026-08-27 02:29 UTCEG score recompute
  74. 2026-08-27 02:29 UTCVendor advisory
  75. 2026-08-27 02:29 UTCGHSA enrichmentGHSA-2g8g-f92j-g4gq · GitHub severity HIGH · GitHub CVSS 8.8

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:36195

Frequently asked(5)

What is CVE-2026-11610?
CVE-2026-11610 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-11610 was made public on July 7, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 7, 2026. EchelonGraph's copy of the record carries a last-modified date of July 8, 2026; the record at its source may have been updated since.
Is CVE-2026-11610 actively exploited?
CVE-2026-11610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11610?
CVE-2026-11610 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11610?
A fix for CVE-2026-11610 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11610 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs