Skip to content
Fencer Intel
high 7.5

CVE-2025-40777 json

A possible assertion failure when 'stale-answer-client-timeout' is set to '0'

published last yr. modified 4mo ago also EUVD-2025-21736

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.

Patch / fix

  • ISC BIND 9 9.18.0, 9.18.11-S1
  • bind9 Debian 14, Debian 13 1:9.20.11-1

debian advisories DEBIAN-CVE-2025-40777

  • bind SLE Module for Server Applications 15 SP7, SLE Module for Basesystem 15 SP7 9.20.11-150700.3.6.1

suse advisories SUSE-SU-2025:02349-1

  • bind openSUSE Tumbleweed 9.20.11-1.1

opensuse advisories openSUSE-SU-2025:15354-1

  • bind Alpine 3.24, Alpine 3.23, Alpine 3.22 9.20.11-r0

alpine advisories ALPINE-CVE-2025-40777

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • bind Azure Linux 3.0 9.20.15-1

azure linux advisories AZL-65553

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2025-40777 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-40777 updated cvss 5.3

bind: bind assertion failure

  • Red Hat Enterprise Linux 6 bind, bind-sdb, bind-libs, bind-utils, bind-chroot Red Hat Enterprise Linux 7 bind, bind-sdb, bind-libs, bind-utils, bind-chroot, bind-pkcs11, +6 more Red Hat Enterprise Linux 8 bind, bind-sdb, bind9.16, bind-libs, bind-utils, bind-chroot, +14 more Red Hat Enterprise Linux 9 bind, dhcp, bind9.18, bind-libs, bind-utils, dhcp-relay, +11 more Red Hat Enterprise Linux 10 bind Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • ISC BIND 9

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.