On this page (7 sections)
On October 27, 2026, the Debian Security Team released DSA-6587-1, an update for the pdns package. Debian describes a parsing error for packets that use compression pointers in the PowerDNS DNS server, which could lead to denial of service. The issue is tracked as CVE-2026-73206.
If you run PowerDNS from Debian 13 (trixie) packages, for example as an authoritative name server for your own or your clients' domains, plan to update. When a DNS server stops answering, the websites, email and APIs that depend on its zones go down with it.
What the advisory says
The advisory is brief. Its one technical statement is that incorrect handling of packets with compression pointers in the PowerDNS DNS server could cause denial of service. The fix for Debian stable (trixie) is version 4.9.18-0+deb13u1, and Debian recommends upgrading the pdns packages. For detailed status it points to the pdns page on the Debian security tracker.
Several things are left open. The advisory does not say which PowerDNS component is affected, whether an unauthenticated remote sender can trigger the problem, or whether the result is a crash or resource exhaustion. It gives no CVSS score and does not mention exploitation. Only one source, the Debian announcement itself, covers this story so far, so treat everything beyond those points as unconfirmed until the tracker or the upstream PowerDNS project says more.
Why compression pointers matter in DNS
DNS messages save space by compressing names. Rather than writing a domain name out again, a message can hold a pointer back to an earlier spot in the same packet. A parser must follow these pointers with care: it has to stay inside the packet and must not be led into loops or endless chains.
Mistakes in this kind of parsing are a familiar weakness class in DNS software. That is general background, not a detail from the advisory, which says only that the parsing was incorrect and could result in denial of service. For a name server, the practical concern is that specially built traffic might stop it from answering queries. The research does not describe the exact mechanism behind CVE-2026-73206.
Who is realistically exposed
- Anyone running the Debian-packaged pdns on trixie, especially servers that answer queries from the public internet.
- Hosting providers and agencies that operate their own authoritative DNS for client domains.
- Teams using PowerDNS internally for service discovery, where a DNS outage would stall applications.
- Users of other distributions or PowerDNS builds from other sources: the advisory covers only the Debian package, so check your own vendor or the upstream project for their status.
If your domains use a managed DNS provider and you do not run pdns yourself, this advisory needs no action from you.
How to check your exposure
Run this on the server to see the installed and candidate pdns package versions. You want the installed version to be 4.9.18-0+deb13u1 or later.
apt policy pdnsIf you are unsure which PowerDNS packages are present, this lists every installed package with pdns in its name, along with its version.
dpkg -l | grep pdnsWhat to do now
- Identify which servers run PowerDNS from Debian trixie packages.
- Check the installed version with apt policy pdns.
- Pick a maintenance window, since the service may restart during the upgrade.
- Upgrade pdns to 4.9.18-0+deb13u1 or later.
- Confirm the server still answers queries for your zones.
- Update secondary name servers too, so no unpatched server stays in rotation.
- Look at the Debian security tracker page for pdns for follow-up details.
The commands below refresh the package lists and then upgrade only the pdns package to the fixed version. Run them on the affected server.
sudo apt update
sudo apt install --only-upgrade pdnsAfterwards, repeat the version check. The output should show 4.9.18-0+deb13u1 or newer.
apt policy pdnsThen check that the server still responds. Replace the placeholders with your server address and a zone you host; a normal answer section with an SOA record means it is working.
dig @YOUR_SERVER_IP YOUR_DOMAIN SOADetection and monitoring afterwards
The advisory gives no indicators of attack, so there is no confirmed log pattern to search for. What you can watch for are the symptoms of the stated impact: the DNS service crashing, restarting repeatedly or becoming unresponsive. This shows the service state and the last 50 log lines from the past day on a systemd-based Debian host; look for unexpected restarts or errors.
systemctl status pdns
journalctl -u pdns --since "1 day ago" | tail -n 50Outside monitoring is useful because a DNS outage shows up from the outside before internal checks notice it. Webforta Monitor covers uptime, certificate and DNS changes, and the uptime monitoring guide explains what to alert on. Monitoring does not remove this flaw, so applying the update is still the step that matters. For more security news and advisories, see the Webforta blog.
Timeline
| Date | Event |
|---|---|
| October 27, 2026 | Debian publishes DSA-6587-1 with fixed pdns 4.9.18-0+deb13u1 for trixie |
The research contains no disclosure date from the PowerDNS project and no reports of exploitation. This article should be updated if that changes.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
