
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2025-59023 is a DNS cache poisoning vulnerability in PowerDNS Recursor that allows unauthenticated remote attackers to poison cached delegations using crafted delegations or IP fragments. It affects PowerDNS Recursor versions 5.1.0–5.1.7, 5.2.0–5.2.5, and 5.3.0. The vulnerability was first tracked in February 2026 and the official advisory was published by PowerDNS. It carries a CVSS v3.1 base score of 8.2 (High) (Red Hat Advisory, PowerDNS Advisory).
The root cause is classified under CWE-345 (Insufficient Verification of Data Authenticity) and CWE-294 (Authentication Bypass by Capture-replay), meaning the Recursor fails to adequately validate the authenticity of DNS delegation responses or IP-fragmented packets before caching them. An attacker can send crafted DNS delegation responses or manipulate IP fragments to inject malicious records into the Recursor's delegation cache without any authentication. This is a network-accessible attack requiring no privileges or user interaction, making it exploitable by any attacker with network access to the resolver. The attack aligns with CAPEC-142 (DNS Cache Poisoning) and CAPEC-141 (Cache Poisoning) patterns (PowerDNS Advisory, Red Hat Bugzilla).
Successful exploitation allows an attacker to poison the DNS delegation cache of affected PowerDNS Recursor instances, redirecting users to attacker-controlled destinations and enabling man-in-the-middle attacks against DNS-dependent services. The primary impact is high integrity loss — DNS responses served to clients can be falsified — with a low availability impact due to potential service disruption. Confidentiality is not directly impacted, but downstream effects such as credential harvesting via redirected traffic are a realistic consequence (Red Hat Advisory, PowerDNS Advisory).
There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (Red Hat Advisory). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is very low at approximately 0.005%, reflecting limited current exploitation probability. No threat actor attribution has been reported (PowerDNS Advisory).
rec_control dump-cache); cached delegations pointing to IP addresses not associated with legitimate authoritative nameservers.PowerDNS has released patched versions: 5.1.8, 5.2.6, and 5.3.1, which address this vulnerability. Organizations should upgrade to one of these fixed versions as the primary remediation. As a network-level workaround, restrict DNS query sources to trusted clients and implement BCP38 (ingress filtering) to reduce IP spoofing risk. Monitoring DNS query logs for suspicious delegation patterns or unusual IP fragments is also recommended (PowerDNS Advisory, Red Hat Advisory).
The PowerDNS blog published the security advisory (2025-06) detailing the vulnerability and patched versions. Debian issued a security advisory (DSA-6045-1) for pdns-recursor, and the issue was discussed on the oss-security mailing list. runZero published a blog post covering the vulnerability in the context of PowerDNS Recursor exposure. Community coverage has been moderate, with aggregation by Tenable (Nessus plugins 271577 and 271978), VulDB, and Linux security news outlets (PowerDNS Blog, runZero Blog, oss-sec).
Fix availability across major Linux distributions and their releases.
bookworm
pdns-recursor
sid
pdns-recursor: 5.3.1-1
trixie
pdns-recursor: 5.2.6-0+deb13u1
bionic (esm-apps)
pdns-recursor
devel
pdns-recursor
focal (esm-apps)
pdns-recursor
jammy
pdns-recursor
jammy (esm-apps)
pdns-recursor
noble
pdns-recursor
noble (esm-apps)
pdns-recursor
resolute
pdns-recursor
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."