CVE-2022-27818: SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname

This month

CRITICAL 9.1REMOTEDOWNGRADE

CVE-2022-27818 is a critical-severity flaw (CVSS 9.1) affecting swhkd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-668
Published	2022-04-07
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: waycrate

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-04-07 02:15 UTCPublished CVE record published
2026-06-17 04:37 UTCUpdated Record last modified

waycrate swhkd DOWNGRADE

Affected: 1.1.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1.5

1. Check installed version

apt-cache policy swhkd || rpm -q swhkd || swhkd --version

2. No fixed release: DOWNGRADE to a release before 1.1.5 (Debian / Ubuntu)

apt-cache madison swhkd sudo apt install swhkd=<VERSION_BEFORE_1.1.5> sudo apt-mark hold swhkd

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list swhkd sudo dnf downgrade swhkd-<VERSION_BEFORE_1.1.5> sudo dnf versionlock add swhkd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-27818?

swhkd: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-27818 being exploited?

CVE-2022-27818 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-27818 affect?

CVE-2022-27818 affects swhkd. Severity is critical (CVSS 9.1). SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service.

How urgent is CVE-2022-27818?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-27819 MEDIUM 5.3 DOWNGRADE SWHKD 1.1.5 allows unsafe parsing via the -c option
CVE-2022-27817 MEDIUM 4.4 DOWNGRADE SWHKD 1.1.5 consumes the keyboard events of unintended users
CVE-2022-27816 HIGH 7.1 DOWNGRADE SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname
CVE-2022-27815 HIGH 7.8 DOWNGRADE SWHKD 1.1.5 unsafely uses the /tmp/swhkd.pid pathname
CVE-2022-27814 LOW 3.3 DOWNGRADE SWHKD 1.1.5 allows arbitrary file-existence tests via the -c option.

References

← Back to latest CVEs