CVE-2025-59024: PowerDNS Recursor · Insufficient Verification of Data Authenticity
Affects PowerDNS RecursorSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 5.3.1 : update PowerDNS Recursor when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.3.1, 5.2.6, 5.1.8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Upgrade Recursor and pdns-recursor to 5.3.1, 5.2.6 or 5.1.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PowerDNSRecursor | Affected
| Fixed in
|
GitHubpdns-recursorpkg:github/pdns-recursorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-59024, European organizations should prioritize the following actions: 1) Monitor PowerDNS vendor communications closely and apply security patches promptly once released, as no patches were linked at the time of disclosure. 2) Implement network-level filtering to block or scrutinize fragmented IP packets, which are used in the exploitation vector, using firewalls or intrusion prevention systems configured to detect suspicious fragmentation patterns. 3) Employ DNSSEC validation on recursive resolvers to ensure authenticity and integrity of DNS data, mitigating the impact of cache poisoning attacks. 4) Restrict network access to DNS resolvers to trusted clients and networks, reducing exposure to remote attackers. 5) Conduct regular DNS traffic analysis and anomaly detection to identify unusual delegation changes or cache poisoning attempts. 6) Consider deploying additional DNS security solutions such as response rate limiting and query logging to enhance detection and response capabilities. 7) Educate network and security teams about the specific nature of this vulnerability to ensure rapid incident response if exploitation is suspected.
Description
Crafted delegations or IP fragments can poison cached delegations in Recursor.