Skip to main content
Mallory
HighVulnerability

CVE-2025-40780: DNS Cache Poisoning via Predictable PRNG in ISC BIND 9

Published Oct 22, 2025 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.6High · v3.1
EPSS0.47%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-40780CWE-341 · Predictable from Observable State

CVE-2025-40780 is a remote DNS cache-poisoning vulnerability in ISC BIND 9 operating as a recursive resolver or forwarder. BIND uses the xoshiro128** pseudorandom number generator for outbound DNS transaction IDs, UDP source ports, and RRset shuffling. Under exploitable circumstances, observable outputs allow attackers to predict subsequent query parameters, undermining the entropy used to distinguish legitimate DNS responses from forged ones. Spoofed responses matching those parameters can be accepted and cached. Affected versions are 9.16.0–9.16.50, 9.18.0–9.18.39, 9.20.0–9.20.13, 9.21.0–9.21.12, 9.16.8-S1–9.16.50-S1, 9.18.11-S1–9.18.39-S1, and 9.20.9-S1–9.20.13-S1. Authoritative-only deployments are not affected by this resolver cache-poisoning issue.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises DNS resolution integrity by inserting attacker-selected records into the resolver cache. Subsequent clients querying affected records can receive forged answers and be redirected to attacker-controlled systems, potentially facilitating phishing, credential theft, malware distribution, interception attempts, or censorship. These downstream outcomes depend on application-layer protections and the records poisoned; the vulnerability does not itself establish arbitrary code execution or privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

No general BIND configuration workaround is identified as a substitute for patching. Restrict recursion to trusted clients to reduce exposure, but do not treat access restrictions as correcting the PRNG weakness. DNS Cookies are not a reliable standalone mitigation because some attack scenarios remain possible with cookies enabled. On affected F5 BIG-IP DNS systems, disable the 'Use BIND Server on BIG-IP' option in the applicable DNS profile where operationally feasible; this can affect configurations relying on BIND fallback.

Remediation

Patch, then assume compromise.

Upgrade to BIND 9.18.41, 9.20.15, 9.21.14, or a later supported fixed release. Supported Preview Edition users should install 9.18.41-S1, 9.20.15-S1, or a later applicable fixed release. The fix replaces the affected generator with a cryptographically secure PRNG. Migrate discontinued branches, including 9.16, to a supported fixed branch. For distribution-packaged or appliance-integrated BIND, install the vendor's security update containing the fix; affected F5 BIG-IP DNS deployments require a vendor-designated fixed release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-40780 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2025-40780 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-40780?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2025-40780.
Is there a patch for CVE-2025-40780?
Upgrade to BIND 9.18.41, 9.20.15, 9.21.14, or a later supported fixed release. Supported Preview Edition users should install 9.18.41-S1, 9.20.15-S1, or a later applicable fixed release.
How severe is CVE-2025-40780?
CVE-2025-40780 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.47% (41st percentile) as of Nov 4, 2026.
Activity feed

Recent activity

40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 3, 2026EulerOS Virtualization 2.13.0 : bind (EulerOS-SA-2026-1625) | Tenable®A weakness in BIND 9's PRNG can allow attackers to predict DNS query source ports and query IDs under specific circumstances. Affected releases include 9.16.0–9.16.50, 9.18.0–9.18.39, 9.20.0–9.20.13, 9.21.0–9.21.12, and specified subscription editions. The advisory identifies affected bind packages in EulerOS Virtualization 2.13.0 and recommends updating them. The plugin reports exploit availability, but its detection relies on self-reported package versions rather than exploitation testing.Read more ↗tenable nessus pluginsNews · Sep 18, 2026EulerOS Virtualization 2.11.1 : bind (EulerOS-SA-2026-3402) | Tenable®A remotely reachable, low-complexity, unauthenticated vulnerability with high integrity impact and changed scope, affecting EulerOS BIND-related packages.Read more ↗tenable nessus pluginsNews · Sep 18, 2026EulerOS Virtualization 2.11.0 : bind (EulerOS-SA-2026-3489) | Tenable®A remotely exploitable, low-complexity vulnerability requiring no privileges or user interaction that can cause high integrity impact; it is addressed in Huawei EulerOS 2.11.0 BIND packages.Read more ↗cryptika blogNews · Sep 17, 2026BIND DNS Servers Hit by 14 Security Flaws Enabling Cache Poisoning and Remote Crashes | Cryptika CybersecurityHigh-severity BIND UDP-randomization weakness caused by a former PRNG that could make source ports and DNS transaction IDs predictable, facilitating cache-poisoning attempts.Read more ↗
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity19Community discussion across Reddit, Mastodon, and other social sources.