CVE-2022-40188: Knot Resolver · Inefficient Algorithmic Complexity
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 5.5.3 : patch affected systems soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 1.9% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n/a n/a | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2022-40188, European organizations should prioritize upgrading Knot Resolver installations to version 5.5.3 or later, where the vulnerability has been addressed. If immediate upgrade is not feasible, organizations should consider implementing network-level protections such as rate limiting and filtering of DNS responses containing unusually large NS or address record sets from authoritative servers. Deploying anomaly detection systems to monitor for abnormal CPU usage patterns on DNS resolvers can provide early warning of exploitation attempts. Additionally, organizations should review their DNS resolver exposure to the internet and restrict access to trusted networks where possible. Employing DNS response validation and caching strategies can reduce the processing load on resolvers. Regularly auditing DNS infrastructure configurations and applying security patches promptly will further reduce risk. Finally, maintaining up-to-date incident response plans that include DNS service disruptions will help organizations respond effectively to potential attacks exploiting this vulnerability.
Description
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.
References
- gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1343 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/S2VE5K3VDUHJOIA2IGT3G5R76IBADMNE/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HIMDNIUI7GTUEKIBBYYW7OCTJQFPDNXL/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XO6LIVQS62MI5GG4OVYB5RHVZMYNHAHG/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2022/10/msg00008.html (opens in a new tab)