Quick answers
- Is CVE-2026-101341 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101341 being exploited in the wild.
- How severe is CVE-2026-101341?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- NLnet Labs NSD 4.10.0 through 4.15.2.
- Is there a fix for CVE-2026-101341?
- Yes: fixed in NSD 4.15.3. Until then: Apply the patch manually to NSD 4.15.2 using the provided patch file and recompile with 'make install', or upgrade to NSD 4.15.3 or later. Restrict zone file uploads and provisioning system access to trusted operators only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101341 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-101341?
- Check whether you run NLnet Labs NSD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: NSD 4.15.3
Apply the patch manually to NSD 4.15.2 using the provided patch file and recompile with 'make install', or upgrade to NSD 4.15.3 or later. Restrict zone file uploads and provisioning system access to trusted operators only.
Technical details
The vulnerability exists in NSD's zone file parser, which fails to validate that text tokens in RDATA fields under 32 bytes remain within allocated stack space. This allows an attacker to craft a zone file with oversized text strings that overflow the stack, overwriting a callback function pointer that is invoked immediately after parsing. The attack vector is local file loading and requires the operator to feed a malicious zone file directly to NSD.
Affected products
- NLnet Labs NSD 4.10.0 through 4.15.2
Timeline
- 2026-10-14: disclosed
- 2026-10-14: patched: NSD 4.15.3 released with fix