cve.bz

CVE-2026-52684 powerdns recursor

3.7 lowEPSS 0.2%

Low (3.7) in powerdns recursor. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
If the auth responds very slowly and the records expire in between, the capping of TTLs is not enforced for lack of data. This does not happen on regular resolve as then then the child records are used immediately if not expired and thus valid, or the records are expired, and in that case not used. So this case can only happen if almost expired records are used to refresh the authoritative NS records.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th 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: no · Technical impact: partial, assessed 2026-07-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-52684 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-52684?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-52684?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-2026-52684 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-2026-52684

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-2026-52684](https://cve.bz/cve/badge/CVE-2026-52684.svg)](https://cve.bz/cve/CVE-2026-52684)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PowerDNS Recursorfrom 0.0.0 before 5.5.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14pdns-recursorno fix listedDEBIAN-CVE-2026-52684
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 4 morepdns-recursorno fix listedUBUNTU-CVE-2026-52684
openSUSETumbleweedpdns-recursor5.4.8-1.1openSUSE-SU-2026:12532-1

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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

References

Check your stackJSON