Overview 46 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 2 EPSS ≥ 0.5
46matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
2EPSS ≥ 0.54.3%
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
46
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
46
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
2
4.3%
No public exploit
44
95.7%
split by
peak 16 / year
20053
Not applicable3
Medium3
not blocked3
No public exploit3
20062
Not applicable2
Medium2
not blocked2
No public exploit2
20070
20084
Not applicable4
Medium4
not blocked4
No public exploit4
20090
20100
20110
20122
Not applicable2
Medium2
not blocked2
No public exploit2
20130
20142
Not applicable2
Medium2
not blocked2
Forecast only1
No public exploit1
20151
Not applicable1
Medium1
not blocked1
Forecast only1
20161
Not applicable1
Medium1
not blocked1
No public exploit1
20170
20188
Not applicable8
Medium8
not blocked8
No public exploit8
20192
Not applicable2
Medium2
not blocked2
No public exploit2
20202
Not applicable2
Medium2
not blocked2
No public exploit2
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
202616
Not applicable16
Medium16
not blocked16
No public exploit16
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-42396 | Medium | 2026-05-21 | Not applicable | No public exploit | Insufficient Validation of Member Zone Data May Cause Catalog Zone Transfer to Fail |
| CVE-2026-41999 | Medium | 2026-05-21 | Not applicable | No public exploit | Incorrect Behaviour of Views with TCP PROXY Requests |
| CVE-2026-33611 | Medium | 2026-04-22 | Not applicable | No public exploit | An operator allowed to use the REST API can cause the Authoritative server to produce invalid HTTPS or SVCB record data, which can in turn cause LMDB database corruption, if using the LMDB backend. |
| CVE-2026-33609 | Medium | 2026-04-22 | Not applicable | No public exploit | Incomplete escaping of LDAP queries when running with 8bit-dns enabled allows users to perform queries of internal domain subtrees. |
| 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-33596 | Medium | 2026-04-22 | Not applicable | No public exploit | A client might theoretically be able to cause a mismatch between queries sent to a backend and the received responses by sending a flood of perfectly timed queries that are routed to a TCP-only or DNS over TLS backend. |
| 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-24029 | Medium | 2026-03-31 | Not applicable | No public exploit | When the early_acl_drop (earlyACLDrop in Lua) option is disabled (default is enabled) on a DNS over HTTPs frontend using the nghttp2 provider, the ACL check is skipped, allowing all clients to send DoH queries regardless of the configured ACL. |
| CVE-2026-0397 | Medium | 2026-03-31 | Not applicable | No public exploit | When the internal webserver is enabled (default is disabled), an attacker might be able to trick an administrator logged to the dashboard into visiting a malicious website and extract information about the running configuration from the dashboard. The root cause of the issue is a misconfiguration of the Cross-Origin Resource Sharing (CORS) policy. |
| CVE-2026-0396 | Medium | 2026-03-31 | Not applicable | No public exploit | An attacker might be able to inject HTML content into the internal web dashboard by sending crafted DNS queries to a DNSdist instance where domain-based dynamic rules have been enabled via either DynBlockRulesGroup:setSuffixMatchRule or DynBlockRulesGroup:setSuffixMatchRuleFFI. |
| 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-17482 | Medium | 2020-10-02 | Not applicable | No public exploit | An issue has been found in PowerDNS Authoritative Server before 4.3.1 where an authorized user with the ability to insert crafted records into a zone might be able to leak the content of uninitialized memory. |
| 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-2019-10203 | Medium | 2019-11-22 | Not applicable | No public exploit | PowerDNS Authoritative daemon , pdns versions 4.0.x before 4.0.9, 4.1.x before 4.1.11, exiting when encountering a serial between 2^31 and 2^32-1 while trying to notify a slave leads to DoS. |
| CVE-2019-10163 | Medium | 2019-07-30 | Not applicable | No public exploit | A Vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.9, 4.0.8 allowing a remote, authorized master server to cause a high CPU load or even prevent any further updates to any slave zone by sending a large number of NOTIFY messages. Note that only servers configured as slaves are affected by this issue. |
| CVE-2018-14663 | Medium | 2018-11-26 | Not applicable | No public exploit | An issue has been found in PowerDNS DNSDist before 1.3.3 allowing a remote attacker to craft a DNS query with trailing data such that the addition of a record by dnsdist, for example an OPT record when adding EDNS Client Subnet, might result in the trailing data being smuggled to the backend as a valid record while not seen by dnsdist. This is an issue when dnsdist is deployed as a DNS Firewall and used to filter some records that should not be received by the backend. This issue occurs only when either the 'useClientSubnet' or the experimental 'addXPF' parameters are used when declaring a new backend. |
| 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-2016-6172 | Medium | 2016-09-26 | Not applicable | No public exploit | PowerDNS (aka pdns) Authoritative Server before 4.0.1 allows remote primary DNS servers to cause a denial of service (memory exhaustion and secondary DNS server crash) via a large (1) AXFR or (2) IXFR response. |
| CVE-2015-5311 | Medium | 2015-11-17 | Not applicable | Forecast only | PowerDNS (aka pdns) Authoritative Server 3.4.4 before 3.4.7 allows remote attackers to cause a denial of service (assertion failure and server crash) via crafted query packets. |
| 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-2012-0206 | Medium | 2012-02-17 | Not applicable | No public exploit | common_startup.cc in PowerDNS (aka pdns) Authoritative Server before 2.9.22.5 and 3.x before 3.0.1 allows remote attackers to cause a denial of service (packet loop) via a crafted UDP DNS response. |
| CVE-2008-5277 | Medium | 2008-12-09 | Not applicable | No public exploit | PowerDNS before 2.9.21.2 allows remote attackers to cause a denial of service (daemon crash) via a CH HINFO query. |
| CVE-2008-3337 | Medium | 2008-08-08 | Not applicable | No public exploit | PowerDNS Authoritative Server before 2.9.21.1 drops malformed queries, which might make it easier for remote attackers to poison DNS caches of other products running on other servers, a different issue than CVE-2008-1447 and CVE-2008-3217. |
| 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. |
| CVE-2006-2069 | Medium | 2006-04-27 | Not applicable | No public exploit | The recursor in PowerDNS before 3.0.1 allows remote attackers to cause a denial of service (application crash) via malformed EDNS0 packets. |
| CVE-2005-0038 | Medium | 2005-12-31 | Not applicable | No public exploit | The DNS implementation of PowerDNS 2.9.16 and earlier allows remote attackers to cause a denial of service via a compressed DNS packet with a label length byte with an incorrect offset, which could trigger an infinite loop. |
| CVE-2005-2301 | Medium | 2005-07-19 | Not applicable | No public exploit | PowerDNS before 2.9.18, when running with an LDAP backend, does not properly escape LDAP queries, which allows remote attackers to cause a denial of service (failure to answer ldap questions) and possibly conduct an LDAP injection attack. |
| CVE-2005-0428 | Medium | 2005-05-02 | Not applicable | No public exploit | The DNSPacket::expand method in dnspacket.cc in PowerDNS before 2.9.17 allows remote attackers to cause a denial of service by sending a random stream of bytes. |