p PatchFirst

PatchFirst · Latest vulnerabilities

pdns-recursor vulnerabilities · Page 2

Vulnerabilities published for pdns-recursor in the last 30 days: 7. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 34

  1. CVE-2026-33259

    Medium · CVSS 5EPSS 0.22%No fix published

    Concurrent modification of RPZ data can lead to denial of servce

    Having many concurrent transfers of the same RPZ can lead to inconsistent RPZ data, use after free and/or a crash of the recursor. Normally concurrent transfers of the same RPZ zone can only occur with a malfunctioning RPZ provider.

    Published Updated
  2. CVE-2026-33601

    Medium · CVSS 4.4EPSS 0.51%No fix published

    Insufficient validation of zonemd record

    If you use the zoneToCache function with a malicious authoritative server, an attacker can send a zone that result in a null pointer dereference, caused by a missing consistency check and leading to a denial of service.

    Published Updated
  3. CVE-2025-59029

    Medium · CVSS 5.3EPSS 0.37%No fix published

    Internal logic flaw in cache management can lead to a denial of service in PowerDNS Recursor

    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.

    Published Updated
  4. CVE-2025-30192

    High · CVSS 7.5EPSS 0.27%No fix published

    A Recursor configured to send out ECS enabled queries can be sensitive to spoofing attempts

    An attacker spoofing answers to ECS enabled requests sent out by the Recursor has a chance of success higher than non-ECS enabled queries. The updated version include various mitigations against spoofing attempts of ECS enabled queries by chaining ECS enabled requests and enforcing stricter validation of the received answers. The most strict mitigation done when the new setting outgoing.edns_subnet_harden (old style name edns-subnet-harden) is enabled.

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →