CVE-2026-101341
8.7HighPublished 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-121
Impact
Attackers who can feed malicious zone files to NSD can achieve remote code execution via stack corruption. Exploitation requires low privileges or control over a provisioning pipeline that supplies the zone files.
Root cause
A stack-based buffer overflow occurs because text tokens in RDATA under 32 bytes are not bounds-checked against the allocated buffer space, overwriting an immediately invoked callback function pointer.
Affected systems
NLnet Labs NSD; specific version ranges are not listed in the advisory data.
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade NSD to the patched release referenced in the NLnet Labs advisory. As an interim workaround, ensure zone files are only ingested if generated by NSD itself or strictly validated before being fed to the daemon.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Tokens of text in RDATA (of for example TXT records) under 32 bytes are not checked to stay within the space reserved for the RDATA allowing for arbitrary sized out of bound stack writes, including an overwrite of a callback function pointer which is called directly after parse. Zone files which are written out by NSD itself, such for zones for which the NSD instance is secondary, will not be formatted like this. The zone file must be fed to NSD directly, (but it could come, for example, from an operator controlled provisioning system).