Is CVE-2026-52686 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-52686 being exploited in the wild.

How severe is CVE-2026-52686?

Low severity, with a CVSS score of 3.7, published 23 July 2026.

Which products and versions are affected?

Powerdns Recursor 5.2.0 to 5.2.11, 5.3.0 to 5.3.8, 5.4.0 to 5.4.3.

Is there a fix for CVE-2026-52686?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-52686 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-52686?

Check whether you run Powerdns Recursor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-52686: PowerDNS Recursor DNSSEC validation bypass in wildcard CNAME/DNAME records

CVE-2026-52686 · Severity: low · CVSS 3.7 · Published 2026-07-23

PowerDNS Recursor, a service used to look up internet addresses, contains a flaw in how it verifies secure website records. An attacker could potentially bypass security checks (DNSSEC) to provide incorrect address information when specific record types like CNAME or DNAME are used. While this could lead to users being directed to the wrong destination, the attack is difficult to execute and does not directly expose private data.

Technologies: Powerdns Recursor. Vendors: Powerdns.

Quick answers

Is CVE-2026-52686 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-52686 being exploited in the wild.
How severe is CVE-2026-52686?: Low severity, with a CVSS score of 3.7, published 23 July 2026.
Which products and versions are affected?: Powerdns Recursor 5.2.0 to 5.2.11, 5.3.0 to 5.3.8, 5.4.0 to 5.4.3.
Is there a fix for CVE-2026-52686?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-52686 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-52686?: Check whether you run Powerdns Recursor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A DNSSEC validation bypass exists in PowerDNS Recursor's DNSSEC validation module, specifically within 'syncres.cc'. The vulnerability occurs when the recursor processes wildcard expansion proofs (NSEC or NSEC3 records); it fails to perform proper signature validation if the resulting wildcard answer is a CNAME or DNAME record. A remote attacker can exploit this to inject unvalidated DNS data into the cache. The attack requires a high degree of complexity to successfully time and spoof the necessary records. Patches are available in versions 5.2.12, 5.3.9, and 5.4.4.

Affected products

PowerDNS Recursor 5.2.0 to 5.2.11, 5.3.0 to 5.3.8, 5.4.0 to 5.4.3

Timeline

2026-07-23: disclosed
2026-07-23: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.