cve.bz

CVE-2025-40775 isc bind 9: Improper Handling of Undefined Values

7.5 highEPSS 15%

High (7.5) in isc bind 9. EPSS 15% estimated probability of exploitation activity in the next 30 days.

On this page
When an incoming DNS protocol message includes a Transaction Signature (TSIG), BIND always checks it. If the TSIG contains an invalid value in the algorithm field, BIND immediately aborts with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.8 and 9.21.0 through 9.21.7.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
15% (unchanged from 15% a week ago; 15% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th 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: yes · Technical impact: partial, assessed 2025-05-21. 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-232 Improper Handling of Undefined Values
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-40775 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-40775?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-40775?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-2025-40775 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.8
ISC BIND 9from 9.21.0 through 9.21.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14bind91:9.20.9-1DEBIAN-CVE-2025-40775
Ubuntu25.04bind91:9.20.4-3ubuntu1.1USN-7526-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7bind9.20.9-150700.3.3.1SUSE-SU-2025:01787-1
openSUSETumbleweedbind9.20.9-1.1openSUSE-SU-2025:15156-1
Alpinev3.18, v3.19, v3.20 and 1 morebind9.18.37-r0ALPINE-CVE-2025-40775
Alpinev3.22, v3.23, v3.24bind9.20.9-r0ALPINE-CVE-2025-40775
Azure Linux3bind9.20.9-1AZL-61972
Alpaquitastreambind9.20.9-r0BELL-CVE-2025-40775

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 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 · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

No Red Hat products or offerings are affected by this vulnerability as the affected code is not used in Red Hat systems.

Although Red Hat does not ship this vulnerable code, we rated the impact of this vulnerability for the upstream community users marked as Important rather than a Moderate flaw because it triggers an assertion failure within BIND's core DNS handling logic, specifically in the TSIG validation path. Unlike typical input validation errors, which might allow an attacker to manipulate a single query's processing, this bug results in a complete and immediate crash of the named daemon. Since both authoritative servers and resolvers perform TSIG verification, the vulnerability can be exploited remotely by an unauthenticated attacker to cause repeated service outages, effectively disrupting DNS resolution for entire domains or networks.

Red Hat's mitigation

Mitigation is either unavailable or does not meet Red Hat Product Security standards for usability, deployment, applicability, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10bindNot affected
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-2025-40775.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • AlexSvobo/nhi-zero-trust-bypass Harbor Check: matches CVE 6 stars, created
    Demonstrates a real-world zero-trust bypass by exploiting BIND CVE-2025-40775 to disrupt DNS, break secret rotation, and expose static cred…

References

Check your stackJSON