CVE-2026-9064

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls within the default maximum BER message size (2 MB), causing excessive CPU consumption and heap allocation on the server. Under concurrent exploitation, this leads to significant latency degradation, worker thread starvation, or out-of-memory termination, resulting in a denial of service.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
52.6%
KEV
Not listed

Published

May 20, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated May 20, 2026
Patch available. Sources: redhat.
redhat

2480093 – (CVE-2026-9064) CVE-2026-9064 389-ds-base: 389-ds-base: unbounded LDAP controls count in get_ldapmessage_controls_ext() causes CPU and heap amplification (remote DoS)

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

cve-details

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

Vendor Advisories for CVE-2026-9064(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
redhatdirsrv/dirsrv-container-rhel10:17817141232026-06-18redhat
redhat389-ds-base-0:2.8.0-7.el9_82026-06-17redhat
redhat389-ds-base-0:3.2.0-7.el10_22026-06-17redhat
redhat389-ds-base-0:3.0.6-18.el10_02026-06-17redhat
redhat389-ds-base-0:2.2.4-18.el9_22026-06-17redhat
redhat389-ds-base-0:2.4.5-25.el9_42026-06-17redhat
redhat389-ds-base-0:2.6.1-21.el9_62026-06-17redhat
redhatredhat-ds:11-8060020260609102432.0ca98e7e2026-06-17redhat
redhatredhat-ds:11-8100020260601104139.37ed7c032026-06-17redhat
redhat389-ds-base-0:1.3.11.1-12.el7_92026-06-17redhat
redhat389-ds:1.4-8100020260601102239.25e700aa2026-06-17redhat
redhat389-ds:1.4-8040020260609102422.96015a922026-06-17redhat
redhat389-ds:1.4-8060020260609102416.824efc522026-06-17redhat
redhatredhat-ds:11-8080020260610130252.f969626e2026-06-17redhat
redhatredhat-ds:12-9020020260615123354.1674d5742026-06-17redhat
redhat389-ds:1.4-8080020260610125847.6dbb38032026-06-17redhat
redhatredhat-ds:12-9040020260611130021.1674d5742026-06-17redhat

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 8× in last 7d / 99× 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.

Showing the most recent 100 of 145 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-9064?
CVE-2026-9064 is a high vulnerability published on May 20, 2026. A flaw was found in 389-ds-base. The getldapmessagecontrols_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls…
When was CVE-2026-9064 disclosed?
CVE-2026-9064 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9064 actively exploited?
CVE-2026-9064 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9064?
CVE-2026-9064 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9064?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9064, 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-9064

Explore →

Is Your Infrastructure Affected by CVE-2026-9064?

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

Start Free Scan →Browse All CVEs