<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: knot resolver</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2023-46317: Knot Resolver before 5.7.0 performs many TCP reconnections upon receiving certain nonsensical responses from s</title><link>https://patchthecve.com/cve/CVE-2023-46317.html</link><guid>https://patchthecve.com/cve/CVE-2023-46317.html</guid><pubDate>Wed, 17 Jun 2026 06:30:39 +0000</pubDate><description>HIGH 7.5: Knot Resolver before 5.7.0 performs many TCP reconnections upon receiving certain nonsensical responses from servers.</description></item><item><title>CVE-2023-26249: Knot Resolver before 5.6.0 enables attackers to consume its resources, launching amplification attacks and pot</title><link>https://patchthecve.com/cve/CVE-2023-26249.html</link><guid>https://patchthecve.com/cve/CVE-2023-26249.html</guid><pubDate>Wed, 17 Jun 2026 05:42:54 +0000</pubDate><description>HIGH 7.5: Knot Resolver before 5.6.0 enables attackers to consume its resources, launching amplification attacks and potentially causing a denial of service. Specifically, a single client query may lead to a hundred TCP connection attempts if a DNS server closes connections without providing a response.</description></item><item><title>CVE-2022-40188: Knot Resolver before 5.5.3 allows remote attackers to cause a denial of service (CPU consumption) because of a</title><link>https://patchthecve.com/cve/CVE-2022-40188.html</link><guid>https://patchthecve.com/cve/CVE-2022-40188.html</guid><pubDate>Wed, 17 Jun 2026 05:01:04 +0000</pubDate><description>HIGH 7.5: Knot Resolver before 5.5.3 allows remote attackers to cause a denial of service (CPU consumption) because of algorithmic complexity. During an attack, an authoritative server must return large NS sets or address sets.</description></item><item><title>CVE-2022-32983: Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions</title><link>https://patchthecve.com/cve/CVE-2022-32983.html</link><guid>https://patchthecve.com/cve/CVE-2022-32983.html</guid><pubDate>Wed, 17 Jun 2026 04:48:19 +0000</pubDate><description>MEDIUM 5.3: Knot Resolver through 5.5.1 may allow DNS cache poisoning when there is an attempt to limit forwarding actions by filters.</description></item><item><title>CVE-2021-40083: Knot Resolver before 5.3.2 is prone to an assertion failure, triggerable by a remote attacker in an edge case </title><link>https://patchthecve.com/cve/CVE-2021-40083.html</link><guid>https://patchthecve.com/cve/CVE-2021-40083.html</guid><pubDate>Wed, 17 Jun 2026 04:06:29 +0000</pubDate><description>HIGH 7.5: Knot Resolver before 5.3.2 is prone to an assertion failure, triggerable by a remote attacker in an edge case (NSEC3 with too many iterations used for a positive wildcard proof).</description></item><item><title>CVE-2018-1110: A flaw was found in knot-resolver before version 2.3.0</title><link>https://patchthecve.com/cve/CVE-2018-1110.html</link><guid>https://patchthecve.com/cve/CVE-2018-1110.html</guid><pubDate>Wed, 17 Jun 2026 01:50:30 +0000</pubDate><description>HIGH 7.5: A flaw was found in knot-resolver before version 2.3.0. Malformed DNS messages may cause denial of service.</description></item><item><title>CVE-2020-12667: Knot Resolver before 5.1.1 allows traffic amplification via a crafted DNS answer from an attacker-controlled s</title><link>https://patchthecve.com/cve/CVE-2020-12667.html</link><guid>https://patchthecve.com/cve/CVE-2020-12667.html</guid><pubDate>Wed, 17 Jun 2026 02:52:06 +0000</pubDate><description>HIGH 7.5: Knot Resolver before 5.1.1 allows traffic amplification via a crafted DNS answer from an attacker-controlled server, aka an &quot;NXNSAttack&quot; issue. This is triggered by random subdomains in the NSDNAME in NS records.</description></item><item><title>CVE-2019-19331: knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization</title><link>https://patchthecve.com/cve/CVE-2019-19331.html</link><guid>https://patchthecve.com/cve/CVE-2019-19331.html</guid><pubDate>Wed, 17 Jun 2026 02:26:30 +0000</pubDate><description>HIGH 7.5: knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A record</description></item><item><title>CVE-2013-5661: Cache Poisoning issue exists in DNS Response Rate Limiting.</title><link>https://patchthecve.com/cve/CVE-2013-5661.html</link><guid>https://patchthecve.com/cve/CVE-2013-5661.html</guid><pubDate>Tue, 16 Jun 2026 23:59:12 +0000</pubDate><description>MEDIUM 5.9: Cache Poisoning issue exists in DNS Response Rate Limiting.</description></item><item><title>CVE-2019-10191: A vulnerability was discovered in DNS resolver of knot resolver before version 4.1.0 which allows remote attac</title><link>https://patchthecve.com/cve/CVE-2019-10191.html</link><guid>https://patchthecve.com/cve/CVE-2019-10191.html</guid><pubDate>Wed, 17 Jun 2026 02:10:27 +0000</pubDate><description>HIGH 7.5: A vulnerability was discovered in DNS resolver of knot resolver before version 4.1.0 which allows remote attackers to downgrade DNSSEC-secure domains to DNSSEC-insecure state, opening possibility of domain hijack using attacks against insecure DNS protocol.</description></item><item><title>CVE-2019-10190: A vulnerability was discovered in DNS resolver component of knot resolver through version 3.2.0 before 4.1.0 w</title><link>https://patchthecve.com/cve/CVE-2019-10190.html</link><guid>https://patchthecve.com/cve/CVE-2019-10190.html</guid><pubDate>Wed, 17 Jun 2026 02:10:27 +0000</pubDate><description>HIGH 7.5: A vulnerability was discovered in DNS resolver component of knot resolver through version 3.2.0 before 4.1.0 which allows remote attackers to bypass DNSSEC validation for non-existence answer. NXDOMAIN answer would get passed through to the client even if its DNSSEC validation failed, instead of sen</description></item><item><title>CVE-2018-10920: Improper input validation bug in DNS resolver component of Knot Resolver before 2.4.1 allows remote attacker t</title><link>https://patchthecve.com/cve/CVE-2018-10920.html</link><guid>https://patchthecve.com/cve/CVE-2018-10920.html</guid><pubDate>Wed, 17 Jun 2026 01:34:55 +0000</pubDate><description>MEDIUM 6.8: Improper input validation bug in DNS resolver component of Knot Resolver before 2.4.1 allows remote attacker to poison cache.</description></item><item><title>CVE-2018-1000002: Improper input validation bugs in DNSSEC validators components in Knot Resolver (prior version 1.5.2) allow at</title><link>https://patchthecve.com/cve/CVE-2018-1000002.html</link><guid>https://patchthecve.com/cve/CVE-2018-1000002.html</guid><pubDate>Wed, 17 Jun 2026 01:32:10 +0000</pubDate><description>LOW 3.7: Improper input validation bugs in DNSSEC validators components in Knot Resolver (prior version 1.5.2) allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay.</description></item></channel></rss>