Skip to main content
VulnerabilityPublished Updated

CVE-2025-40778: ISC BIND 9 · Acceptance of Extraneous Untrusted Data With Trusted Data

Affects ISC BIND 9Source CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubisc/bindpkg:github/isc/bindOther threatsAffected
  • >=9.11.0 <=9.16.50
  • 9.18.0 <=9.18.39
  • 9.20.0 <=9.20.13
  • 9.21.0 <=9.21.12
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should monitor ISC advisories closely and apply official patches or updates for BIND 9 as soon as they become available. In the interim, administrators can implement strict DNS response validation policies, such as enabling DNSSEC validation to detect and reject forged records. Restricting recursive DNS queries to trusted clients and limiting exposure of DNS servers to untrusted networks can reduce attack vectors. Network-level protections like firewall rules and intrusion detection systems should be tuned to detect anomalous DNS traffic patterns. Regularly auditing DNS server configurations and logs for suspicious activity can help identify exploitation attempts early. Additionally, deploying redundant DNS infrastructure with diverse software versions can mitigate single points of failure due to this vulnerability.

Description

Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.

References

Community reviews

Loading reviews…