BIND 9 on Linux: which version fixes what

What it is, and why it is on your server

BIND 9 is the most widely deployed DNS server software, packaged as bind9 on Debian and Ubuntu and bind on Rocky and AlmaLinux. It is also what many control panels install to serve a hosting account's zones.

Why its advisories behave the way they do

• A crash is an outage, and named is frequently in front of everything. A specially formed query that kills the daemon takes down mail delivery and site resolution with it.
• Recursion left open is the classic mistake. A resolver that answers the whole internet is both an amplification weapon pointed at someone else and a cache-poisoning target of its own.
• The release cadence is brisk. ISC publishes several advisories a year and the distributions follow closely, so a BIND package more than a few months behind is usually genuinely behind.

Check what you are actually running

The version that matters is the package version, not the upstream one. Distributions backport security fixes without changing the number before the dash, so a release that looks years old is frequently fully patched, and the revision after the dash is the only part that tells you.

dpkg-query -W -f='${Package} ${Version}\n' bind9 bind9-utils 2>/dev/null

rpm -q bind bind-utils

If you are not deliberately running a public resolver, check that you are not accidentally running one: `dig +short @your.server.ip example.com` from outside should not answer.

Fixed versions, per distribution

Each distribution patches on its own schedule and under its own version scheme, so the same CVE has a different answer on each of them. These come from the distributions’ own advisory data, asked per release. Where a release has no fixed version, that is what the advisory says, not a gap in the data.

Advisory data last refreshed 26 September 2026. It is re-read daily.

What this page does not tell you

It does not tell you whether your server is affected. A CVE applying to a package is not the same as a CVE applying to your installation: the fix may already be backported into what you are running, the vulnerable module may not be loaded, or the service may not be reachable from anywhere that matters. Answering that needs the versions on your machine, not a list.

It also carries no count of how many servers are affected. SecAI monitors a small fleet, and a percentage drawn from it would be arithmetic on a sample too small to mean anything. When that changes, the number will appear here and the page will say when it started.

Read next