Nsd vulnerabilitiesRanked by how likely they are to be used.
Nsd is made by Nlnetlabs. We track 4 published vulnerabilities in it, across 83 versions. None of them is on the list of flaws known to be exploited today. If you run Nsd, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Nsd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Nsd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Nsd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 9.2%CVE-2012-2978Medium
query.c in NSD 3.0.x through 3.0.8, 3.1.x through 3.1.1, and 3.2.x before 3.2.12 allows remote attackers to cause a denial of service (NULL pointer dereference and child process crash) via a crafted DNS packet.
- 3.5%CVE-2013-5661Medium
Cache Poisoning issue exists in DNS Response Rate Limiting.
- 3.2%CVE-2009-1755Medium
Off-by-one error in the packet_read_query_section function in packet.c in nsd 3.2.1, and process_query_section in query.c in nsd 2.3.7, allows remote attackers to cause a denial of service (crash) and possibly...
- 2.9%CVE-2016-6173High
NSD before 4.1.11 allows remote DNS master servers to cause a denial of service (/tmp disk consumption and slave server crash) via a zone transfer with unlimited data.
- 0.5%CVE-2026-12245High
NSD from version 4.13.0 has a heap use-after-free bug in logging errors on TLS connections, causing a crash of the server process, which can be triggered trivially by sending a DNS query over a DoT connection, and...
- 0.4%CVE-2026-12246High
NSD version 4.14.0 introduced a bug where a specially crafted APL RR, with an adflength larger than permitted for the address family will overwrite the stack when the zone is written to disk, with a maximum of 111...
- 0.2%CVE-2026-12490High
When a provide-xfr is given with a tls-auth-name, a secondary requesting a transfer should provide a client certificate with that name.
Running Nsd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
query.c in NSD 3.0.x through 3.0.8, 3.1.x through 3.1.1, and 3.2.x before 3.2.12 allows remote attackers to cause a denial of service (NULL pointer dereference and child process crash) via a crafted DNS packet.
- Matched to
- Nsd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Nsd, across 83 versions.
None of Nsd's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Nsd. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.