CVE-2026-58224

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-08-14. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Samba's CTDB, the clustered database service used by Samba. Insufficient integrity validation of received CTDB protocol packets allows malformed packets containing invalid field lengths, improperly terminated strings, or inconsistent packet sizes to be processed without adequate bounds checking. A remote attacker with access to the CTDB private network may trigger a denial of service through process crashes or excessive memory consumption and, in limited cases, disclose adjacent memory contents.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 14, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available. Sources: redhat.
generic

Samba - Security Announcement Archive

https://www.samba.org/samba/security/CVE-2026-58224-advisory.html
generic

16085 – (CVE-2026-58224) [SECURITY] CVE-2026-58224: CTDB: heap OOB read via unchecked packet length fields

https://bugzilla.samba.org/show_bug.cgi?id=16085
redhat

2502720 – (CVE-2026-58224) CVE-2026-58224 samba: CTDB fails to do integrity checking of received packets

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

CVE-2026-58224 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Vendor Advisories for CVE-2026-58224(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuwinbind (2:4.23.6+dfsg-1ubuntu2.2) @ resolute2026-10-04ubuntu

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:12(1)
PackageVulnerable rangeFix by version rangeDependents
samba2:4.17.10+dfsg-0+deb12u1 ... 2:4.25.0~rc1+dfsg-1 (177 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
samba2:4.22.10+dfsg-0+deb13u1 ... 2:4.22.8+dfsg-0+deb13u2 (9 versions)
  • every version up to 2:4.22.10+dfsg-0+deb13u2: fixed in 2:4.22.10+dfsg-0+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
samba2:4.22.3+dfsg-4 ... 2:4.24.5+dfsg-1~bpo13+1 (34 versions)
  • every version up to 2:4.24.5+dfsg-1: fixed in 2:4.24.5+dfsg-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 95× 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 189 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-58224?
CVE-2026-58224 is a medium vulnerability published on August 14, 2026. A flaw was found in Samba's CTDB, the clustered database service used by Samba. Insufficient integrity validation of received CTDB protocol packets allows malformed packets containing invalid field lengths, improperly terminated strings, or inconsistent packet sizes to be processed without adequate…
When was CVE-2026-58224 disclosed?
CVE-2026-58224 was first published on August 14, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58224 actively exploited?
CVE-2026-58224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58224?
CVE-2026-58224 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58224?
A fix for CVE-2026-58224 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58224 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-58224

Explore →

Is Your Infrastructure Affected by CVE-2026-58224?

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

Book a Demo →Browse All CVEs