CVE-2026-12244: NSD AXFR Heap Overflow and Remote Code Execution Vulnerability
NSD, the authoritative DNS server from NLnet Labs, contains a critical vulnerability in how it processes zone transfers from a primary DNS server. When configured as a secondary server, NSD can be crashed and potentially exploited for remote code execution if an attacker controls the primary server and sends a specially crafted DNS SVCB record during a zone transfer. The vulnerability stems from an integer overflow in a variable used to allocate memory for the record, allowing an attacker to write up to 65,509 bytes to heap memory.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-122, CWE-190
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-25 / 2026-06-26
NVD description (verbatim)
If NSD is configured as secondary for a zone, the primary of that zone can crash NSD with an AXFR containing a DNS message with a special crafted SVCB RR with an rdata size of 65512, that let's an (uint16_t) variable that is used to allocate space needed for the RR wrap (because total size > 65535), causing a heap overflow. The attacker can perform a controlled (RCE class) head write of up to 65509 bytes
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12244 is a heap overflow vulnerability affecting NSD's AXFR (zone transfer) handling. The flaw occurs when NSD processes an SVCB (Service Binding) Resource Record with an rdata size of exactly 65,512 bytes during a zone transfer from a primary server. A 16-bit unsigned integer variable used to calculate the required allocation space wraps due to the total message size exceeding 65,535 bytes (the maximum 16-bit value). This integer overflow results in undersized heap allocation, leading to a buffer overflow. The vulnerability is classified under CWE-122 (Heap-based Buffer Overflow) and CWE-190 (Integer Overflow or Wraparound), and enables controlled heap writes of up to 65,509 bytes, potentially allowing remote code execution.
Business impact
Organizations running NSD as a secondary DNS server face significant risk if their primary DNS infrastructure is compromised or if an attacker gains the ability to intercept or spoof primary server responses. Successful exploitation could result in complete compromise of the DNS server process, leading to service disruption, data exfiltration, or lateral movement within the network. DNS infrastructure is foundational to business operations; its compromise could cascade to affect all dependent services. The requirement for authenticated zone transfers (PR:L in the CVSS vector) provides some organizational protection if primary servers are properly secured and access is restricted, but does not eliminate the risk.
Affected systems
NSD (authoritative DNS server) from NLnet Labs is affected. The vulnerability is specific to NSD instances configured as secondary servers that accept zone transfers from a primary. The exact affected versions are not specified in the advisory data; organizations should consult the NLnet Labs security advisories and release notes to determine which versions contain the fix. Any NSD deployment using secondary zone configuration is potentially at risk.
Exploitability
Exploitation requires authentication as a primary DNS server or the ability to spoof primary server responses to the vulnerable secondary NSD instance. The attacker must craft a zone transfer response containing the malicious SVCB record. While the vulnerability is deterministic and does not require user interaction, successful exploitation is limited to threat actors with network access to the primary-secondary relationship or those who can perform DNS protocol-level attacks. The CVSS vector reflects a low complexity attack (AC:L) requiring only low privileges (PR:L), indicating the vulnerability is straightforward to trigger once the necessary network access is established. The vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog.
Remediation
Apply security patches from NLnet Labs as soon as they become available. Verify the specific patched version against the vendor's advisory. Until patching is possible, implement network segmentation to restrict zone transfers to trusted primary servers only, and consider using DNSSEC validation and primary-secondary authentication mechanisms to prevent spoofed zone transfers. Monitor zone transfer activity and alert on unexpected SVCB records or AXFR failures.
Patch guidance
Contact NLnet Labs or visit their security advisories page to identify the patched NSD version addressing CVE-2026-12244. Apply patches to all NSD instances configured as secondary servers. Test the patched version in a staging environment to ensure zone transfers and DNS resolution continue to function correctly before deploying to production. Verify that the patch is compatible with your existing DNS configuration and any other software that depends on NSD's specific version or behavior.
Detection guidance
Monitor NSD logs for AXFR zone transfer errors or unexpected crashes, particularly after receiving zone transfers. Network detection can focus on AXFR traffic containing unusually large or malformed SVCB records. Implement baseline monitoring of NSD process stability and memory usage; the heap overflow may produce detectable anomalies or crashes before successful code execution. Consider deploying DNS firewall rules to validate SVCB record structure and size during zone transfers, though this requires DNS-aware inspection capabilities.
Why prioritize this
This vulnerability merits immediate attention due to its HIGH CVSS score (8.8), potential for remote code execution, and the critical nature of DNS infrastructure. Although it requires authenticated or spoofed primary server access, the impact—complete server compromise—justifies treating it as a high-priority patch. Organizations should prioritize secondary NSD servers that accept transfers from less-trusted or internet-facing primary servers, or where multiple zones are transferred.
Risk score, explained
The CVSS 3.1 score of 8.8 (HIGH) reflects the combination of network-accessible attack vector, low attack complexity, low privilege requirements, and high impact across confidentiality, integrity, and availability. The score appropriately weights the severity of heap overflow vulnerabilities that enable RCE, balanced against the requirement for authenticated access to the zone transfer protocol. This score does not account for organizational risk context such as network segmentation or primary server security posture.
Frequently asked questions
Does this vulnerability affect NSD if it is only configured as a primary server?
No. The vulnerability is specific to NSD configured as a secondary server receiving zone transfers from a primary. Primary-only NSD configurations are not affected by this flaw.
What network access is required to exploit this vulnerability?
An attacker must be able to send a zone transfer response to the vulnerable NSD secondary, either by compromising the primary server, spoofing its responses, or intercepting the zone transfer traffic. Standard DNS secondary-to-primary communication is required; the attacker does not need general internet access to arbitrary NSD instances.
Can this vulnerability be exploited without causing a visible crash?
The vulnerability results in a heap overflow, which may allow controlled memory writes. While a crash is likely if exploitation is not carefully crafted, a skilled attacker may be able to achieve RCE without triggering an immediate denial of service, making the vulnerability particularly dangerous.
Is there a workaround if we cannot patch immediately?
Restrict zone transfers to authenticated, trusted primary servers only. Implement firewall rules to limit which hosts can initiate zone transfers to your secondary NSD. Additionally, monitor zone transfer activity closely and be prepared to manually trigger failover or restart NSD if instability is detected. However, these are temporary mitigations; patching is essential.
This analysis is based on the CVE record and publicly available information as of the publication date. Vulnerability severity and exploitability may evolve as additional research is published or as threat actors develop novel attack techniques. Organizations should verify patch availability and compatibility with their specific NSD version and deployment configuration against official NLnet Labs advisories before remediation. This document is provided for informational purposes and does not constitute professional security advice; consult with your organization's security team and DNS administrator for guidance specific to your environment. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2023-29146HIGHInteger Overflow in Malwarebytes EDR 1.0.11 Linux Hash Functions
- CVE-2023-43688HIGHMalwarebytes Heap Buffer Overflow Denial of Service Vulnerability
- CVE-2025-14098HIGHAvira Antivirus Engine Heap Buffer Overflow—Patch Guidance
- CVE-2025-66280HIGHQNAP Integer Overflow Vulnerability: Patch & Risk Assessment
- CVE-2026-0059HIGHAndroid Heap Buffer Overflow in SDP Discovery – Remote Code Execution
- CVE-2026-0095HIGHAndroid Bluetooth Integer Overflow Privilege Escalation
- CVE-2026-0100HIGHAndroid Heap Buffer Overflow Local Privilege Escalation
- CVE-2026-0131HIGHAndroid RTP Integer Overflow Privilege Escalation Vulnerability