cve.bz

CVE-2025-59029 powerdns recursor: Reachable Assertion

5.3 mediumEPSS 0.4%

Medium (5.3) in powerdns recursor. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
An attacker can trigger an assertion failure by requesting crafted DNS records, waiting for them to be inserted into the records cache, then send a query with qtype set to ANY.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-12-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-59029 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-59029?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-59029?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-59029 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-59029

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-59029](https://cve.bz/cve/badge/CVE-2025-59029.svg)](https://cve.bz/cve/CVE-2025-59029)

HTML:

<a href="https://cve.bz/cve/CVE-2025-59029"><img src="https://cve.bz/cve/badge/CVE-2025-59029.svg" alt="CVE-2025-59029"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PowerDNS Recursorfrom 5.3.0 before 5.3.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14pdns-recursor5.3.3-1DEBIAN-CVE-2025-59029
Ubuntu24.04:LTS, 25.10, 26.04:LTS and 5 morepdns-recursorno fix listedUBUNTU-CVE-2025-59029
openSUSETumbleweedpdns-recursor5.4.8-1.1openSUSE-SU-2026:12532-1
Alpinev3.23, v3.24pdns-recursor5.3.1-r1ALPINE-CVE-2025-59029

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate for Red Hat because an attacker can trigger an assertion failure in PowerDNS by requesting crafted DNS records and then sending a query with qtype set to ANY. This could lead to a denial of service for the PowerDNS service.

Red Hat's mitigation

To mitigate this issue, restrict network access to the PowerDNS service to only trusted clients or networks. This can be achieved by configuring firewall rules to limit incoming connections to the PowerDNS port (typically UDP/TCP 53). For example, using `firewalld`: `sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_NETWORK>" port port="53" protocol="udp" accept'` and `sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_NETWORK>" port port="53" protocol="tcp" accept'`. After applying firewall rules, reload the firewall: `sudo firewall-cmd --reload`. This may impact legitimate DNS resolution if not configured carefully. A service restart may be required for changes to take full effect.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-59029.

References

Check your stackJSON