Possible heap buffer overflow when validator canonicalizes RDATA that contains domain name
CVE-2026-56416 is fixed in 12 products on 1 platform, first by DEBIAN-CVE-2026-56416, released July 28, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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 'datstart + dname_valid(datstart, ...)' and passes it straight to 'query_dname_tolower()' 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 'query_dname_tolower()' to walk label-by-label through stale bytes in the per-worker 'env->scratch_buffer', past the end of that heap allocation if 'msg-buffer-size' 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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| python3-unbound · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| python3-unbound-debuginfo · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound · Debian 13.5 (trixie) | 1.26.1-0+deb13u1 | DEBIAN-CVE-2026-56416 | Jul 28, 2026 |
| unbound · Debian 14 | 1.25.2-1 | DEBIAN-CVE-2026-56416 | Jul 28, 2026 |
| unbound · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound · opensuse-leap 16.0 | 1.25.2-160000.1.1 | OPENSUSE-SU-2026:21550-1 | Aug 10, 2026 |
| unbound · sles 15.6 | 1.25.2-150600.23.19.1 | SUSE-SU-2026:3885-1 | Aug 31, 2026 |
| unbound · sles 15.7 | 1.25.2-150600.23.19.1 | SUSE-SU-2026:3885-1 | Aug 31, 2026 |
| unbound · sles 16.0 | 1.25.2-160000.1.1 | SUSE-SU-2026:23226-1 | Aug 10, 2026 |
| unbound-anchor · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-anchor-debuginfo · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-debuginfo · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-debugsource · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-devel · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-libs · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-libs-debuginfo · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-utils · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
| unbound-utils-debuginfo · amzn 2023 | 1.17.1-1.amzn2023.0.13 | ALAS2023-2026-2033 | Aug 3, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.