cve.bz

CVE-2026-33612 powerdns recursor

7.5 highEPSS 0.1%

High (7.5) in powerdns recursor. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A malicious authoritative server can send a crafted zone via the ZoneToCache function that leads to cache poisoning.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th 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-06-25. 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-349 Acceptance of Extraneous Untrusted Data With Trusted Data
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

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

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

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PowerDNS Recursorfrom 5.2.0 before 5.2.11
PowerDNS Recursorfrom 5.3.0 before 5.3.8
PowerDNS Recursorfrom 5.4.0 before 5.4.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12pdns-recursorno fix listedDEBIAN-CVE-2026-33612
Debian13pdns-recursor5.2.11-0+deb13u1DEBIAN-CVE-2026-33612
Debian14pdns-recursor5.4.3-1DEBIAN-CVE-2026-33612
Ubuntu24.04:LTS, 25.10, 26.04:LTS and 5 morepdns-recursorno fix listedUBUNTU-CVE-2026-33612
openSUSETumbleweedpdns-recursor5.4.8-1.1openSUSE-SU-2026:12532-1
Alpinev3.24pdns-recursor5.4.3-r0ALPINE-CVE-2026-33612

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.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON