CVE-2025-59030: PowerDNS Recursor · Incorrect Default Permissions
Affects PowerDNS RecursorSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% 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:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PowerDNS Recursor | Affected
| Fixed in– |
AI-suggested
- Monitor DNS traffic for unusual or unexpected NOTIFY queries over TCP and implement alerting mechanisms.
- Apply vendor patches promptly once available to address the underlying permission and validation issues.
- In the interim, restrict or block incoming TCP NOTIFY queries at the network perimeter or firewall to prevent exploitation.
- Harden DNS recursor configurations by disabling unnecessary features or query types if possible.
- Employ rate limiting on DNS queries to mitigate potential DoS amplification.
- Conduct regular audits of DNS server configurations and permissions to ensure adherence to security best practices.
- Use network segmentation to isolate DNS infrastructure and limit exposure to untrusted networks.
- Collaborate with upstream DNS providers and peers to detect and respond to anomalous DNS traffic patterns.
- Prepare incident response plans specific to DNS service disruptions to minimize downtime and impact.
Description
An attacker can trigger the removal of cached records by sending a NOTIFY query over TCP.