Overview 25 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 1 EPSS ≥ 0.5
25matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
1EPSS ≥ 0.54.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
25
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
25
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
1
4.0%
No public exploit
24
96.0%
split by
peak 8 / year
20061
Not applicable1
Medium1
not blocked1
No public exploit1
20070
20082
Not applicable2
Medium2
not blocked2
No public exploit2
20090
20100
20110
20121
Not applicable1
Medium1
not blocked1
No public exploit1
20130
20142
Not applicable2
Medium2
not blocked2
Forecast only1
No public exploit1
20150
20160
20170
20187
Not applicable7
Medium7
not blocked7
No public exploit7
20190
20201
Not applicable1
Medium1
not blocked1
No public exploit1
20210
20221
Not applicable1
Medium1
not blocked1
No public exploit1
20231
Not applicable1
Medium1
not blocked1
No public exploit1
20240
20251
Not applicable1
Medium1
not blocked1
No public exploit1
20268
Not applicable8
Medium8
not blocked8
No public exploit8
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-33601 | Medium | 2026-04-22 | Not applicable | No public exploit | 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. |
| CVE-2026-33600 | Medium | 2026-04-22 | Not applicable | No public exploit | An RPZ sent by a malicious authoritative server can result in a null pointer dereference, caused by a missing consistency check and leading to a denial of service. |
| CVE-2026-33262 | Medium | 2026-04-22 | Not applicable | No public exploit | An attacker can send replies that result in a null pointer dereference, caused by a missing consistency check and leading to a denial of service. Cookies are disabled by default. |
| CVE-2026-33261 | Medium | 2026-04-22 | Not applicable | No public exploit | A zone transition from NSEC to NSEC3 might trigger an internal inconsistency and cause a denial of service. |
| CVE-2026-33259 | Medium | 2026-04-22 | Not applicable | No public exploit | 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. |
| CVE-2026-24027 | Medium | 2026-02-09 | Not applicable | No public exploit | Crafted zones can lead to increased incoming network traffic. |
| CVE-2026-0398 | Medium | 2026-02-09 | Not applicable | No public exploit | Crafted zones can lead to increased resource usage and crafted CNAME chains can lead to cache poisoning in Recursor. |
| CVE-2025-59024 | Medium | 2026-02-09 | Not applicable | No public exploit | Crafted delegations or IP fragments can poison cached delegations in Recursor. |
| CVE-2025-59029 | Medium | 2025-12-09 | Not applicable | No public exploit | 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. |
| CVE-2023-26437 | Medium | 2023-04-04 | Not applicable | No public exploit | Denial of service vulnerability in PowerDNS Recursor allows authoritative servers to be marked unavailable.This issue affects Recursor: through 4.6.5, through 4.7.4 , through 4.8.3. |
| CVE-2022-37428 | Medium | 2022-08-23 | Not applicable | No public exploit | PowerDNS Recursor up to and including 4.5.9, 4.6.2 and 4.7.1, when protobuf logging is enabled, has Improper Cleanup upon a Thrown Exception, leading to a denial of service (daemon crash) via a DNS query that leads to an answer with specific properties. |
| CVE-2020-14196 | Medium | 2020-07-01 | Not applicable | No public exploit | In PowerDNS Recursor versions up to and including 4.3.1, 4.2.2 and 4.1.16, the ACL restricting access to the internal web server is not properly enforced. |
| CVE-2018-14644 | Medium | 2018-11-09 | Not applicable | No public exploit | An issue has been found in PowerDNS Recursor from 4.0.0 up to and including 4.1.4. A remote attacker sending a DNS query for a meta-type like OPT can lead to a zone being wrongly cached as failing DNSSEC validation. It only arises if the parent zone is signed, and all the authoritative servers for that parent zone answer with FORMERR to a query for at least one of the meta-types. As a result, subsequent queries from clients requesting DNSSEC validation will be answered with a ServFail. |
| CVE-2016-7074 | Medium | 2018-09-11 | Not applicable | No public exploit | An issue has been found in PowerDNS before 3.4.11 and 4.0.2, and PowerDNS recursor before 4.0.4, allowing an attacker in position of man-in-the-middle to alter the content of an AXFR because of insufficient validation of TSIG signatures. A missing check that the TSIG record is the last one, leading to the possibility of parsing records that are not covered by the TSIG signature. |
| CVE-2016-7073 | Medium | 2018-09-11 | Not applicable | No public exploit | An issue has been found in PowerDNS before 3.4.11 and 4.0.2, and PowerDNS recursor before 4.0.4, allowing an attacker in position of man-in-the-middle to alter the content of an AXFR because of insufficient validation of TSIG signatures. A missing check of the TSIG time and fudge values was found in AXFRRetriever, leading to a possible replay attack. |
| CVE-2017-15094 | Medium | 2018-01-23 | Not applicable | No public exploit | An issue has been found in the DNSSEC parsing code of PowerDNS Recursor from 4.0.0 up to and including 4.0.6 leading to a memory leak when parsing specially crafted DNSSEC ECDSA keys. These keys are only parsed when validation is enabled by setting dnssec to a value other than off or process-no-validate (default). |
| CVE-2017-15093 | Medium | 2018-01-23 | Not applicable | No public exploit | When api-config-dir is set to a non-empty value, which is not the case by default, the API in PowerDNS Recursor 4.x up to and including 4.0.6 and 3.x up to and including 3.7.4 allows an authorized user to update the Recursor's ACL by adding and removing netmasks, and to configure forward zones. It was discovered that the new netmask and IP addresses of forwarded zones were not sufficiently validated, allowing an authenticated user to inject new configuration directives into the Recursor's configuration. |
| CVE-2017-15092 | Medium | 2018-01-23 | Not applicable | No public exploit | A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inject HTML and Javascript code into the web interface, altering the content. |
| CVE-2017-15090 | Medium | 2018-01-23 | Not applicable | No public exploit | An issue has been found in the DNSSEC validation component of PowerDNS Recursor from 4.0.0 and up to and including 4.0.6, where the signatures might have been accepted as valid even if the signed data was not in bailiwick of the DNSKEY used to sign it. This allows an attacker in position of man-in-the-middle to alter the content of records by issuing a valid signature for the crafted records. |
| CVE-2014-8601 | Medium | 2014-12-10 | Not applicable | Forecast only | PowerDNS Recursor before 3.6.2 does not limit delegation chaining, which allows remote attackers to cause a denial of service ("performance degradations") via a large or infinite number of referrals, as demonstrated by resolving domains hosted by ezdns.it. |
| CVE-2014-3614 | Medium | 2014-09-19 | Not applicable | No public exploit | Unspecified vulnerability in PowerDNS Recursor (aka pdns_recursor) 3.6.x before 3.6.1 allows remote attackers to cause a denial of service (crash) via an unknown sequence of malformed packets. |
| CVE-2012-1193 | Medium | 2012-02-17 | Not applicable | No public exploit | The resolver in PowerDNS Recursor (aka pdns_recursor) 3.3 overwrites cached server names and TTL values in NS records during the processing of a response to an A record query, which allows remote attackers to trigger continued resolvability of revoked domain names via a "ghost domain names" attack. |
| CVE-2008-3217 | Medium | 2008-07-18 | Not applicable | No public exploit | PowerDNS Recursor before 3.1.6 does not always use the strongest random number generator for source port selection, which makes it easier for remote attack vectors to conduct DNS cache poisoning. NOTE: this is related to incomplete integration of security improvements associated with addressing CVE-2008-1637. |
| CVE-2008-1637 | Medium | 2008-04-02 | Not applicable | No public exploit | PowerDNS Recursor before 3.1.5 uses insufficient randomness to calculate (1) TRXID values and (2) UDP source port numbers, which makes it easier for remote attackers to poison a DNS cache, related to (a) algorithmic deficiencies in rand and random functions in external libraries, (b) use of a 32-bit seed value, and (c) choice of the time of day as the sole seeding information. |
| CVE-2006-4252 | Medium | 2006-11-14 | Not applicable | No public exploit | PowerDNS Recursor 3.1.3 and earlier allows remote attackers to cause a denial of service (resource exhaustion and application crash) via a CNAME record with a zero TTL, which triggers an infinite loop. |