In NLnetLabs Unbound up to and including 1.26.0, a degradation of service vulnerability is present in the TCP/DoT reading procedure where there is no limit on consecutive reads. A malicious actor that can stream and sustain a rate of distinct uncached names over the TCP/DoT connection, monopolizes a single worker's entire event loop for as long as its writes stay ahead of the drain.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade unbound-debuginfoUpgrade unbound-develUpgrade unboundUpgrade unbound-utilsUpgrade python3-unboundUpgrade unbound-libsUpgrade unbound-anchorUpgrade unbound-libs-debuginfoUpgrade python3-unbound-debuginfoUpgrade unbound-debugsourceUpgrade unbound-anchor-debuginfoUpgrade unbound-utils-debuginfo | Sep 30, 2026 | Sep 16, 2026 |
| Debian | — | Upgrade unbound | Sep 21, 2026 | Sep 16, 2026 |
| Freebsd | — | Upgrade unbound | Sep 18, 2026 | Sep 16, 2026 |
| Redhat_linux | — | No solution exists | Sep 22, 2026 | Sep 16, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub