CVE-2026-3119: Authenticated query containing a TKEY record may cause named to terminate unexpectedly
Authenticated query containing a TKEY record may cause named to terminate unexpectedly
Other sources
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-S1 are NOT affected.
— NVD
Affected Software
Remediation
Information
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-3119?
CVE-2026-3119 has been classified as a high severity vulnerability due to its potential to cause named to terminate unexpectedly.
How do I fix CVE-2026-3119?
To fix CVE-2026-3119, you should upgrade to BIND 9 version 9.20.21 or version 9.21.20.
Which versions of BIND 9 are affected by CVE-2026-3119?
CVE-2026-3119 affects BIND 9 versions 9.20.0 to 9.20.20, and 9.21.0 to 9.21.19.
What causes CVE-2026-3119 to occur?
CVE-2026-3119 occurs when processing a signed query containing a TKEY record under specific conditions.
Is there a workaround for CVE-2026-3119?
There is no known workaround for CVE-2026-3119; patching to the latest version is recommended.