In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| NLnet Labs | Unbound | 0 ~ 1.26.1 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-81642 | 9.1 CRITICAL | Heap buffer overflow and possible Remote Code Execution when digesting DNSKEY |
| CVE-2026-82717 | 8.4 HIGH | CNAME synthesis could lead to heap corruption |
| CVE-2026-78227 | 6.5 MEDIUM | Use-after-free in DoQ stream output buffer on reset re-transmission |
| CVE-2026-82720 | 5.9 MEDIUM | Use-after-free in DoH stream cleanup code path |
| CVE-2026-85501 | 5.3 MEDIUM | Retrap: Novel Vulnerabilities to launch Algorithmic Complexity Attacks on DNSSEC |
| CVE-2026-80225 | 5.3 MEDIUM | Possible degradation of service from continuous queries on the same TCP/DoT connection |
| CVE-2026-77955 | 4.4 MEDIUM | Possible ZONEMD verification bypass window |
| CVE-2026-77860 | 3.7 LOW | 'serve-expired' can bypass Unbound 'wait-limit' |
No comments yet