Skip to main content
Mallory
MediumVulnerability

CVE-2026-3119: BIND 9 TSIG-Authenticated TKEY Query Denial of Service

Published Mar 25, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.60%49th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-3119CWE-617 · Reachable Assertion

CVE-2026-3119 is a reachable assertion vulnerability in BIND 9 named TKEY query processing. A correctly TSIG-authenticated query containing a TKEY record can reach a condition in dns_tkey_processquery() where a NULL key-name value is used during response construction. This causes an assertion failure and terminates the named daemon. TKEY DELETE requests and certain invalid TKEY modes can trigger the affected path. BIND 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and Supported Preview Edition 9.20.9-S1 through 9.20.20-S1 are affected. BIND 9.18.x is not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes named to abort, producing a denial of service for authoritative DNS service, recursive resolution, or both, depending on the affected deployment. A single crafted authenticated query may be sufficient to terminate the daemon.

Mitigation

If you can’t patch tonight, do this now.

There is no practical protocol-level workaround. Restrict possession and use of TSIG credentials to trusted entities, remove unnecessary TSIG keys where operationally feasible, and protect configured TSIG key material from disclosure. Monitor for unexpected named process exits and restarts.

Remediation

Patch, then assume compromise.

Upgrade to a fixed BIND release: BIND 9.20.21 or later, or BIND 9.21.20 or later. Distribution-maintained BIND packages should be updated to the vendor version incorporating the upstream fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-3119 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-3119 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3119?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-3119.
Is there a patch for CVE-2026-3119?
Upgrade to a fixed BIND release: BIND 9.20.21 or later, or BIND 9.21.20 or later. Distribution-maintained BIND packages should be updated to the vendor version incorporating the upstream fix.
What products are affected by CVE-2026-3119?
Internet Systems Consortium Bind.
How severe is CVE-2026-3119?
CVE-2026-3119 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.60% (49th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.