-@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025101500 10800 3600 604800 10800
+@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025102201 10800 3600 604800 10800
@ 3600 IN NS pdns-public-ns1.powerdns.com.
@ 3600 IN NS pdns-public-ns2.powerdns.com.
recursor-5.0.9.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.0.10.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.0.11.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
-recursor-5.0.12.security-status 60 IN TXT "2 Unsupported release (EOL)"
+recursor-5.0.12.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
recursor-5.1.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.1.0-beta1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.1.0-rc1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.1.3.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.1.4.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.1.5.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
-recursor-5.1.6.security-status 60 IN TXT "1 OK"
-recursor-5.1.7.security-status 60 IN TXT "1 OK"
+recursor-5.1.6.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
+recursor-5.1.7.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
+recursor-5.1.8.security-status 60 IN TXT "1 OK"
+
recursor-5.2.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.0-beta1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.0-rc1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.1.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.2.2.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.2.3.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
-recursor-5.2.4.security-status 60 IN TXT "1 OK"
-recursor-5.2.5.security-status 60 IN TXT "1 OK"
+recursor-5.2.4.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
+recursor-5.2.5.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
+recursor-5.2.6.security-status 60 IN TXT "1 OK"
+
recursor-5.3.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.3.0-alpha2.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
-recursor-5.3.0-beta1.security-status 60 IN TXT "2 Superseded pre-release"
-recursor-5.3.0-rc1.security-status 60 IN TXT "2 Superseded pre-release"
-recursor-5.3.0.security-status 60 IN TXT "1 OK"
+recursor-5.3.0-beta1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
+recursor-5.3.0-rc1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities"
+recursor-5.3.0.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-06.html"
+recursor-5.3.1.security-status 60 IN TXT "1 OK"
; Recursor Debian
recursor-3.6.2-2.debian.security-status 60 IN TXT "3 Upgrade now, see https://docs.powerdns.com/recursor/appendices/EOL.html"
--- /dev/null
+PowerDNS Security Advisory 2025-06: Crafted delegations or IP fragments can poison cached delegations in Recursor
+=================================================================================================================
+
+- CVE: CVE-2025-59023
+- Date: 15th October 2025
+- Affects: PowerDNS Recursor up to and including 5.1.7, 5.2.5 and 5.3.0
+- Not affected: PowerDNS Recursor 5.1.8, 5.2.6 and 5.3.1
+- Severity: High
+- Impact: Cache pollution
+- Exploit: This problem can be triggered by an attacker spoofing crafted delegations
+- Risk of system compromise: None
+- Solution: Upgrade to patched version
+
+CVSS Score: 8.2, see
+https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L&version=3.1
+
+- CVE: CVE-2025-59024
+- Date: 15th October 2025
+- Affects: PowerDNS Recursor up to and including 5.1.7, 5.2.5 and 5.3.0
+- Not affected: PowerDNS Recursor 5.1.8, 5.2.6 and 5.3.1
+- Severity: Medium
+- Impact: Cache pollution
+- Exploit: This problem can be triggered by an attacker using an UDP IP fragments attack
+- Risk of system compromise: None
+- Solution: Upgrade to patched version
+
+CVSS Score: 6.5 see
+https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L&version=3.1
+
+It has been brought to our attention that the Recursor does not apply strict enough validation of received delegation information.
+The malicious delegation information can be sent by an attacker spoofing packets.
+The patched versions of the Recursor apply strict validation of the received delegation information from authoritative servers.
+In versions 5.2.6 and 5.3.1 the already existing validations are tightened further, while version 5.1.8 contains a full backport of the strict validations.
+Note that other vendors will release updated software to fix similar issues as well.
+
+The remedy is: upgrade to a patched version.
+
+We would like to thank Yuxiao Wu, Yunyi Zhang, Baojun Liu, and Haixin Duan from Tsinghua University and
+Shiming Liu from Network and Information Security Lab, also Tsinghua University for bringing these issues to our attention.