NSD vulnerabilities: known CVEs & security history
NLnet Labs · Network / DNS · 8 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all NSD release lines — 8 in total. A CVE here doesn't mean your version is affected — check NSD's current status and the safe version to run.
Known NSD CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-18664 | critical | 9.1 | 0% | 2026 |
| CVE-2026-12244 | high | 8.8 | 0% | 2026 |
| CVE-2026-12246 | high | 8.1 | 0% | 2026 |
| CVE-2026-19538 | high | 7.5 | 0% | 2026 |
| CVE-2026-19401 | high | 7.5 | 0% | 2026 |
| CVE-2026-18916 | high | 7.5 | 0% | 2026 |
| CVE-2026-12490 | high | 7.5 | 0% | 2026 |
| CVE-2026-12245 | high | 7.5 | 0% | 2026 |
Is my NSD version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your NSD version → · Monitor NSD for new CVEs →
NSD vulnerabilities — frequently asked
How many known vulnerabilities does NSD have?
IsItPatched tracks 8 CVEs for NSD. 1 is critical-severity and 7 high-severity. These span every release line — what matters is whether the version you run is affected.
Does NSD have any actively-exploited vulnerabilities?
None of NSD's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe NSD vulnerability?
Among tracked issues, CVE-2026-18664 (CRITICAL, CVSS 9.1) ranks highest — a Improper access control weakness.
Is NSD safe to use?
It depends on the version. The latest supported NSD release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: NSD security status · NSD end-of-life · actively-exploited CVEs. Always verify against NLnet Labs's advisories — see our disclaimer.