Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-3119: Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record

35
Routine
MEDIUM 6.5UPGRADE

CVE-2026-3119 is a medium-severity flaw (CVSS 6.5) affecting bind. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` configuration. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18.0 through 9.18.46 and 9.18.11-S1 through 9.18.46-

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-617
Published2026-03-25
Last modified2026-06-17
Publisher (CNA): Internet Systems Consortium (ISC) · Vendor: isc

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

isc bind UPGRADE
Affected: >= 9.20.0 and < 9.20.21 · >= 9.21.0 and < 9.21.20
Fixed in: 9.20.21, 9.21.20
Safe to downgrade to: a release before 9.20.0
1. Check installed version
apt-cache policy bind || rpm -q bind || bind --version
2. UPGRADE to 9.20.21 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bind
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bind
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 9.20.0 (Debian / Ubuntu)
apt-cache madison bind sudo apt install bind=<VERSION_BEFORE_9.20.0> sudo apt-mark hold bind
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bind sudo dnf downgrade bind-<VERSION_BEFORE_9.20.0> sudo dnf versionlock add bind
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-3119?

bind: upgrade to 9.20.21, 9.21.20. Exact commands for each OS are on this page.

Is CVE-2026-3119 being exploited?

CVE-2026-3119 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-3119 affect?

CVE-2026-3119 affects bind. Severity is medium (CVSS 6.5). Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the

How urgent is CVE-2026-3119?

Priority 35/100. No elevated risk signals yet.

Software pages

BIND DNS vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.