Low [CVE-2026-54478] DNS Cookie security bypass via incorrect server cookie calculation
This low-severity Red Hat Linux advisory covers CVE-2026-54478 affecting Red Hat Hardened Images, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
A flaw was found in Unbound. When Unbound is configured to listen on a proxy-protocol port with DNS cookies enabled, it incorrectly computes the server cookie using the proxy's network address instead of the actual client's address.
This Low impact flaw in Unbound occurs when the DNS resolver is configured to use both `proxy-protocol-port` and `answer-cookie: yes`. The server cookie is incorrectly derived from the proxy's address, enabling an off-path attacker to bypass DNS Cookie security by replaying a harvested cookie.
This vulnerability requires a specific, non-default configuration and has high attack complexity, limiting its impact. Red Hat severity: Low — CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).
Weakness: CWE-303.
- 1.18.0
- 1.25.1
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
- unbound-main-1.25.2-0.1.hum1
- RHSA-2026:43588
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Mitigation checklist
- To mitigate this issue, avoid enabling `answer-cookie: yes` when Unbound is configured to listen on a `proxy-protocol-port`. If the `proxy-protocol-port` is essential, consider disabling DNS cookies. If both features are required, ensure the proxy infrastructure is secured and trusted. A restart of the Unbound service is required for configuration changes to take effect.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.