cve.bz

CVE-2026-3119 isc bind: Reachable Assertion

6.5 mediumEPSS 0.6%Fix available

Medium (6.5) in isc bind. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-3119 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-3119?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-3119?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-3119 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ISC BIND 9from 9.20.0 through 9.20.20
ISC BIND 9from 9.21.0 through 9.21.19
ISC BIND 9from 9.20.9-S1 through 9.20.20-S1

Fixed in

ProductFixed in
ISC BIND 99.18.0
ISC BIND 99.18.11-S1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13bind91:9.20.21-1~deb13u1DEBIAN-CVE-2026-3119
Debian14bind91:9.20.21-1DEBIAN-CVE-2026-3119
Ubuntu18.04:LTS, 24.04:LTS, 25.10 and 1 moreisc-dhcpno fix listedUBUNTU-CVE-2026-3119
Ubuntu20.04:LTS, 22.04:LTSbind9-libsno fix listedUBUNTU-CVE-2026-3119
Ubuntu25.10bind91:9.20.11-1ubuntu2.2UBUNTU-CVE-2026-3119
Red Hathummingbird:1bind, bind-doc, bind-libs and 4 more0:9.18.48-1.hum1RHSA-2026:6935
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7bind9.20.21-150700.3.18.1SUSE-SU-2026:1351-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0bind9.20.21-160000.1.1SUSE-SU-2026:21204-1
openSUSELeap 16.0bind9.20.21-160000.1.1openSUSE-SU-2026:20550-1
openSUSETumbleweedbind9.20.21-1.1openSUSE-SU-2026:10448-1
Alpinev3.22, v3.23, v3.24bind9.20.21-r0ALPINE-CVE-2026-3119
Azure Linux3bind9.20.21-1AZL-80984
Alpaquita25, streambind9.20.21-r0BELL-CVE-2026-3119

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate impact. A flaw in BIND 9's `named` component can lead to a Denial of Service if an attacker with a valid Transaction Signature (TSIG) key sends a specially crafted query. Red Hat Enterprise Linux 8 and 9 are affected by this vulnerability.

Red Hat's mitigation

To mitigate this issue, restrict access to the `named` service to only trusted networks and clients. If Transaction Signature (TSIG) keys are not actively used or required, consider disabling them in the BIND configuration. If TSIG keys are necessary, ensure they are securely managed and only distributed to authorized clients. After making configuration changes, a restart of the `named` service may be required to apply the changes, which could temporarily impact DNS resolution.

ProductPackageStateAdvisory
Red Hat Hardened Imagesbind-main-9.18.48-1.hum1Fixed 2026-04-07RHSA-2026:6935
Red Hat Enterprise Linux 10bindFix deferred
Red Hat Enterprise Linux 6bindNot affected
Red Hat Enterprise Linux 7bindNot affected
Red Hat Enterprise Linux 8bindNot affected
Red Hat Enterprise Linux 8bind9.16Not affected
Red Hat Enterprise Linux 9bindNot affected
Red Hat Enterprise Linux 9bind9.18Not affected
Red Hat Enterprise Linux 9dhcpNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-3119.

References

Check your stackJSON