Skip to main content
CVE-2025-59030VulnerabilityPublished

CVE-2025-59030: PowerDNS Recursor · Incorrect Default Permissions

Affects PowerDNS RecursorSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
PowerDNS RecursorAffected
  • =5.3.0
  • =5.2.0
  • =5.1.0
Fixed in–

AI-suggested

1. Monitor DNS traffic for unusual or unexpected NOTIFY queries over TCP and implement alerting mechanisms. 2. Apply vendor patches promptly once available to address the underlying permission and validation issues. 3. In the interim, restrict or block incoming TCP NOTIFY queries at the network perimeter or firewall to prevent exploitation. 4. Harden DNS recursor configurations by disabling unnecessary features or query types if possible. 5. Employ rate limiting on DNS queries to mitigate potential DoS amplification. 6. Conduct regular audits of DNS server configurations and permissions to ensure adherence to security best practices. 7. Use network segmentation to isolate DNS infrastructure and limit exposure to untrusted networks. 8. Collaborate with upstream DNS providers and peers to detect and respond to anomalous DNS traffic patterns. 9. 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.

References

Community reviews

Loading reviews…