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.
CVE-2026-58218
Score 5.3 from GitHub Security Advisory published 2026-07-30. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity53% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 30, 2026
Advisory Details (4)
Auto-updated Jul 30, 2026Samba - Security Announcement Archive
https://www.samba.org/samba/security/CVE-2026-58218.html16115 – (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=161152502728 – (CVE-2026-58218) CVE-2026-58218 samba: DNS signing DoS via TKEY name cache exhaustion
https://bugzilla.redhat.com/show_bug.cgi?id=2502728Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | winbind (2:4.23.6+dfsg-1ubuntu2.2) @ resolute | 2026-08-25 | ubuntu |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| samba | 2:4.13.13+dfsg-1 ... 2:4.24.5+dfsg-1~bpo13+1 (245 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| samba | 2:4.17.10+dfsg-0+deb12u1 ... 2:4.24.5+dfsg-1~bpo13+1 (173 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| samba | 2:4.22.10+dfsg-0+deb13u1 ... 2:4.22.8+dfsg-0+deb13u2 (9 versions) | 2:4.22.10+dfsg-0+deb13u2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| samba | 2:4.22.3+dfsg-4 ... 2:4.24.5+dfsg-1~bpo13+1 (34 versions) | 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 24× in last 7d / 105× 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 105 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:46 UTCEG score recompute
- 2026-08-25 02:46 UTCVendor advisory
- 2026-08-25 02:46 UTCGHSA enrichment
- 2026-08-24 05:06 UTCVendor advisory
- 2026-08-24 05:06 UTCGHSA enrichment
- 2026-08-23 07:26 UTCEG score recompute
- 2026-08-23 07:26 UTCVendor advisory
- 2026-08-23 07:26 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 09:46 UTCEG score recompute
- 2026-08-22 09:46 UTCVendor advisory
- 2026-08-22 09:46 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 12:05 UTCEG score recompute
- 2026-08-21 12:05 UTCVendor advisory
- 2026-08-21 12:05 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 14:23 UTCEG score recompute
- 2026-08-20 14:23 UTCVendor advisory
- 2026-08-20 14:23 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:43 UTCVendor advisory
- 2026-08-19 16:43 UTCGHSA enrichment
- 2026-08-18 18:57 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-18 18:57 UTCVendor advisory
- 2026-08-18 18:57 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 21:16 UTCGHSA enrichment
- 2026-08-16 23:36 UTCEG score recompute
- 2026-08-16 23:36 UTCVendor advisory
- 2026-08-16 23:36 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 01:56 UTCVendor advisory
- 2026-08-16 01:56 UTCGHSA enrichment
- 2026-08-15 04:16 UTCEG score recompute
- 2026-08-15 04:16 UTCVendor advisory
- 2026-08-15 04:16 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:35 UTCEG score recompute
- 2026-08-14 06:35 UTCVendor advisory
- 2026-08-14 06:35 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:55 UTCEG score recompute
- 2026-08-13 08:55 UTCVendor advisory
- 2026-08-13 08:55 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 11:16 UTCEG score recompute
- 2026-08-12 11:16 UTCVendor advisory
- 2026-08-12 11:16 UTCGHSA enrichment
- 2026-08-11 13:36 UTCEG score recompute
- 2026-08-11 13:36 UTCVendor advisory
- 2026-08-11 13:36 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 15:56 UTCVendor advisory
- 2026-08-10 15:56 UTCGHSA enrichment
- 2026-08-09 17:51 UTCEG score recompute
- 2026-08-09 17:51 UTCVendor advisory
- 2026-08-09 17:51 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 20:12 UTCEG score recompute
- 2026-08-08 20:12 UTCVendor advisory
- 2026-08-08 20:12 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 22:32 UTCEG score recompute
- 2026-08-07 22:32 UTCVendor advisory
- 2026-08-07 22:32 UTCGHSA enrichment
- 2026-08-07 00:52 UTCEG score recompute
- 2026-08-07 00:52 UTCVendor advisory
- 2026-08-07 00:52 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 03:12 UTCEG score recompute
- 2026-08-06 03:12 UTCVendor advisory
- 2026-08-06 03:12 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 05:33 UTCEG score recompute
- 2026-08-05 05:32 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 07:50 UTCEG score recompute
- 2026-08-04 07:50 UTCVendor advisory
- 2026-08-04 07:50 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 10:10 UTCGHSA enrichment
- 2026-08-02 12:31 UTCEG score recompute
- 2026-08-02 12:31 UTCVendor advisory
- 2026-08-02 12:31 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 14:51 UTCEG score recompute
- 2026-08-01 14:51 UTCVendor advisory
- 2026-08-01 14:51 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 17:11 UTCGHSA enrichment
- 2026-07-30 19:31 UTCEG score recompute
- 2026-07-30 19:31 UTCGHSA enrichment
- 2026-07-30 18:02 UTCEG score recompute
- 2026-07-30 18:02 UTCGHSA enrichment
- 2026-07-30 16:52 UTCEG score recompute
- 2026-07-30 16:52 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-58218?
When was CVE-2026-58218 disclosed?
Is CVE-2026-58218 actively exploited?
What is the CVSS score of CVE-2026-58218?
How do I remediate CVE-2026-58218?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58218
Is Your Infrastructure Affected by CVE-2026-58218?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.