PatchSiren cyber security CVE debrief
CVE-2026-12244 NLnet Labs CVE debrief
CVE-2026-12244 is a high-severity vulnerability in the NSD DNS server. If NSD is configured as a secondary for a zone, an attacker can crash the primary NSD server with a specially crafted AXFR request containing an SVCB RR with an rdata size of 65512. This causes a heap overflow, allowing the attacker to perform a controlled heap write of up to 65509 bytes.
- Vendor
- NLnet Labs
- Product
- NSD
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-25
- Original CVE updated
- 2026-10-25
- Advisory published
- 2026-06-25
- Advisory updated
- 2026-10-25
Who should care
Defenders responsible for NSD DNS server management and security, including operators, platforms, vulnerability management, and security teams, should assess exposure and prioritize patching or mitigating controls. This includes verifying NSD version 4.14.0 to 4.14.3 and applying patches or implementing compensating controls.
Why it matters
CVE-2026-12244 is a high-severity vulnerability in the NSD DNS server that can be exploited for remote code execution or disruption of DNS services. Defenders should prioritize verifying NSD version and applying patches or mitigating controls.
- Potential for controlled heap write, allowing for remote code execution
- Possible disruption of DNS services
- Need for verification of NSD version and patch application
Technical summary
The vulnerability exists in NSD when configured as a secondary for a zone. A specially crafted AXFR request can cause a heap overflow, allowing an attacker to perform a controlled heap write of up to 65509 bytes. This can lead to remote code execution or disruption of DNS services. Defenders should prioritize verifying NSD version and applying patches or mitigating controls to prevent exploitation. Affected product context indicates NSD DNS server management and security teams should assess exposure and prioritize patching.
Defensive priority
Defenders should prioritize verifying NSD version 4.14.0 to 4.14.3 and applying patches or mitigating controls to prevent exploitation.
Recommended defensive actions
- Verify NSD version and apply patches if necessary
- Implement mitigating controls to prevent exploitation
- Monitor NSD logs for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify NSD version 4.14.0 to 4.14.3 and review official advisories for patching guidance. Evidence limits suggest a controlled heap write of up to 65509 bytes. Source grounding indicates a specially crafted AXFR request can cause a heap overflow.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-12244 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-12244
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-12244 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-12244
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.nlnetlabs.nl/downloads/nsd/CVE-2026-12244.txt
[email protected] - Patch, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.