CVE-2026-3119: Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record
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 score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 52%) |
| CISA exploited list | No |
| Weakness | CWE-617 |
| Published | 2026-03-25 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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
Related CVEs
- CVE-2023-2828 HIGH 7.5 UPGRADE MITIGATE Every `named` instance configured to run as a recursive resolver maintains a cache database holding the respon
- CVE-2023-2911 HIGH 7.5 UPGRADE MITIGATE If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes
- CVE-2023-2829 HIGH 7.5 UPGRADE MITIGATE A `named` instance configured to run as a DNSSEC-validating recursive resolver with the Aggressive Use of DNSS
- CVE-2006-2073 MEDIUM 5.0 DOWNGRADE Unspecified vulnerability in ISC BIND allows remote attackers to cause a denial of service via a crafted DNS m
- CVE-2026-1519 HIGH 7.5 UPGRADE If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may