https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2022-27817.htmlhttps://patchthecve.com/cve/CVE-2022-27817.htmlWed, 17 Jun 2026 04:37:34 +0000MEDIUM 4.4: SWHKD 1.1.5 consumes the keyboard events of unintended users. This could potentially cause an information leak, but is usually a denial of functionality.https://patchthecve.com/cve/CVE-2022-27814.htmlhttps://patchthecve.com/cve/CVE-2022-27814.htmlWed, 17 Jun 2026 04:37:33 +0000LOW 3.3: SWHKD 1.1.5 allows arbitrary file-existence tests via the -c option.https://patchthecve.com/cve/CVE-2022-27819.htmlhttps://patchthecve.com/cve/CVE-2022-27819.htmlWed, 17 Jun 2026 04:37:34 +0000MEDIUM 5.3: SWHKD 1.1.5 allows unsafe parsing via the -c option. An information leak might occur but there is a simple denial of service (memory exhaustion) upon an attempt to parse a large or infinite file (such as a block or character device).https://patchthecve.com/cve/CVE-2022-27818.htmlhttps://patchthecve.com/cve/CVE-2022-27818.htmlWed, 17 Jun 2026 04:37:34 +0000CRITICAL 9.1: SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service.https://patchthecve.com/cve/CVE-2022-27816.htmlhttps://patchthecve.com/cve/CVE-2022-27816.htmlWed, 17 Jun 2026 04:37:34 +0000HIGH 7.1: SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data loss or a denial of service.https://patchthecve.com/cve/CVE-2022-27815.htmlhttps://patchthecve.com/cve/CVE-2022-27815.htmlWed, 17 Jun 2026 04:37:33 +0000HIGH 7.8: SWHKD 1.1.5 unsafely uses the /tmp/swhkd.pid pathname. There can be an information leak or denial of service.