# CVE-2026-3119: Authenticated query containing a TKEY record may cause named to terminate unexpectedly

> An authenticated attacker with a valid TSIG key can cause the BIND DNS server to crash by sending a query with a TKEY record.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** ALPINE-CVE-2026-3119, AZL-80984, BELL-CVE-2026-3119, DEBIAN-CVE-2026-3119, GHSA-rrrp-782c-4484, MINI-fggx-64h4-77w3, UBUNTU-CVE-2026-3119

## What is CVE-2026-3119?

CVE-2026-3119 is a medium-severity denial of service vulnerability in Isc Bind, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-3119?

It affects 1 product.


Products: Isc Bind.

## How do I fix CVE-2026-3119?

Apply the vendor's patch.

## Is CVE-2026-3119 being exploited?

There is no known exploitation of CVE-2026-3119 in the wild and no public exploit code.

## Other vulnerabilities in Isc Bind

- [CVE-2008-0122](https://insights.sbomify.com/CVE-2008-0122/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0010](https://insights.sbomify.com/CVE-2001-0010/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0011](https://insights.sbomify.com/CVE-2001-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0013](https://insights.sbomify.com/CVE-2001-0013/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1029](https://insights.sbomify.com/CVE-2000-1029/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3119 and fix it if it is affected.

What it is: CVE-2026-3119 is a medium-severity denial of service vulnerability in Isc Bind, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3119 in the wild and no public exploit code.

Affected product: Isc Bind. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3119/ (Markdown: https://insights.sbomify.com/CVE-2026-3119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3119
- OSV: https://osv.dev/vulnerability/CVE-2026-3119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3119/
Summaries are generated and may contain mistakes; the official description above is the record.