CVE-2026-11774

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

An integer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasl_io_start_packet(), adding sizeof(uint32_t) to a crafted SASL packet length prefix of 0xFFFFFFFC causes unsigned wraparound to zero, bypassing the nsslapd-maxsasliosize limit and leading to a heap buffer overflow of up to approximately 2 megabytes of attacker-controlled data. After a successful SASL bind with integrity protection (SSF > 0), a remote attacker can cause a Denial of Service (DoS) or achieve Remote Code Execution (RCE). In FreeIPA and Red Hat Identity Management deployments, any domain user with a valid Kerberos ticket, enrolled host, or service account can trigger this vulnerability over the network. This flaw is independent of CVE-2025-14905, which patched schema.c only and did not modify sasl_io.c.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity76% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jun 11, 2026
Patch available. Sources: redhat.
redhat

2484916 – (CVE-2026-11774) CVE-2026-11774 389-ds-base: 389-ds-base: integer overflow in SASL packet length bypasses size limit leading to heap buffer overflow

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

cve-details

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdirsrv/dirsrv-container-rhel10:17834521002026-07-08redhat
redhat389-ds-base-0:3.0.6-19.el10_02026-07-08redhat
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
redhatredhat-ds:11-8060020260702180044.0ca98e7e2026-07-07redhat
redhatredhat-ds:11-8100020260702145313.37ed7c032026-07-07redhat
redhatredhat-ds:12-9040020260703055735.1674d5742026-07-07redhat
redhat389-ds-base-0:3.2.0-8.el10_22026-07-07redhat
redhat389-ds-base-0:1.3.11.1-13.el7_92026-07-07redhat
redhat389-ds:1.4-8100020260626120929.25e700aa2026-07-07redhat
redhat389-ds-base-0:2.8.0-8.el9_82026-07-07redhat
redhatredhat-ds:11-8080020260702180836.f969626e2026-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-base-0:2.4.5-26.el9_42026-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 rangeFixed inDependents
389-ds-base1.4.4.11-2 ... 3.1.2+vendor1-2 (23 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
389-ds-base2.3.1+dfsg1-1 ... 3.3.0-2 (16 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
389-ds-base3.1.2+dfsg1-1 ... 3.3.0-2 (6 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 35× 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 305 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-11774?
CVE-2026-11774 is a high vulnerability published on June 11, 2026. An integer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasliostartpacket(), adding sizeof(uint32t) to a crafted SASL packet length prefix of 0xFFFFFFFC causes unsigned wraparound to zero, bypassing the nsslapd-maxsasliosize limit and leading to a heap…
When was CVE-2026-11774 disclosed?
CVE-2026-11774 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11774 actively exploited?
CVE-2026-11774 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 45.1% of all scored CVEs.
What is the CVSS score of CVE-2026-11774?
CVE-2026-11774 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-11774?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11774, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11774

Explore →

Is Your Infrastructure Affected by CVE-2026-11774?

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