CVE-2022-27815 is a critical-severity (CVSS 9.1) CWE-59 vulnerability in Simple-Wayland-HotKey-Daemon. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for Simple-Wayland-HotKey-Daemon — see the affected versions and patch details below.
Insecure Temporary File in SWHKD
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
Simple-Wayland-HotKey-DaemonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
SWHKD is a display protocol-independent hotkey daemon made in Rust. In SWHKD versions 1.1.5 and prior, SWHKD uses the /tmp/swhkd.pid pathname. As /tmp is accessible to all users, there can be an information leak or denial of service. No known workarounds exist. A patch is available on the 1.1.0 branch of the repository.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | Simple-Wayland-HotKey-Daemon | all versions | 1.2.0cargo update -p Simple-Wayland-HotKey-Daemon --precise 1.2.0 |
Affected Products
swhkdwaycrateResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Simple-Wayland-HotKey-Daemon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Simple-Wayland-HotKey-Daemon to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-27815 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-27815 in your dependencies?
Find it across crates.io, including transitive dependencies.