CVE-2026-58218

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-30. A secondary CVSS source baseline 5.3; sources differ by 0.0.

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

A fix is available — apply it.

A flaw was found in Samba's internal DNS server where unauthenticated TKEY registration requests were added to the TKEY name cache before being rejected. A remote, unauthenticated attacker can exploit this behavior by sending a large number of TKEY requests with arbitrary names, exhausting the cache and evicting legitimate TKEY entries. This can prevent legitimate TSIG authentication for signed DNS queries, resulting in a denial of service.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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

July 30, 2026

Last Modified

July 30, 2026

Advisory Details (4)

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

Samba - Security Announcement Archive

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

16115 – (CVE-2026-58218) [SECURITY] CVE-2026-58218: DNS TKEY negotiation stores unauthenticated GSS contexts in a fixed FIFO before authentication completes

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

2502728 – (CVE-2026-58218) CVE-2026-58218 samba: DNS signing DoS via TKEY name cache exhaustion

https://bugzilla.redhat.com/show_bug.cgi?id=2502728
redhatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-58218(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-06ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
samba2:4.13.13+dfsg-1 ... 2:4.24.5+dfsg-1~bpo13+1 (245 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
samba2:4.17.10+dfsg-0+deb12u1 ... 2:4.25.0~rc1+dfsg-1 (178 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 15× in last 7d / 88× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58218?
CVE-2026-58218 is a medium vulnerability published on July 30, 2026. A flaw was found in Samba's internal DNS server where unauthenticated TKEY registration requests were added to the TKEY name cache before being rejected. A remote, unauthenticated attacker can exploit this behavior by sending a large number of TKEY requests with arbitrary names, exhausting the…
When was CVE-2026-58218 disclosed?
CVE-2026-58218 was first published on July 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-58218 actively exploited?
CVE-2026-58218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58218?
CVE-2026-58218 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58218?
A fix for CVE-2026-58218 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58218 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-58218

Explore →

Is Your Infrastructure Affected by CVE-2026-58218?

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