https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 10:10:47 +0000 https://cve.radiocsirt.org/vuln/cve-2026-56416 <p><strong>Affected:</strong> NLnet Labs Unbound</p> <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> <p><strong>Affected:</strong> NLnet Labs Unbound</p> <p>In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as &#39;datstart + dname_valid(datstart, ...)&#39; and passes it straight to &#39;query_dname_tolower()&#39; without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause &#39;query_dname_tolower()&#39; to walk label-by-label through stale bytes in the per-worker &#39;env-&gt;scratch_buffer&#39;, past the end of that heap allocation if &#39;msg-buffer-size&#39; has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.</p> https://cve.radiocsirt.org/vuln/cve-2026-56416