NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

CVE-2022-27816 — Simple-Wayland-HotKey-Dae…

HIGHFix: waycrate/swhkd@0b620a0

CVE-2022-27816 is a high-severity (CVSS 7.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.

Data Loss/Denial of Service in SWHKD

Also known asGHSA-8m49-2xj8-67v9
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk
0.00%0.33%0.67%1.00%0.1%0.5%May 26Sep 26Nov 26

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

1 pkg affected
🦀Simple-Wayland-HotKey-Daemon

Real-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 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data loss or a denial of service. A patch is available on the 1.1.0 branch of the repository.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioSimple-Wayland-HotKey-Daemonall versions1.2.0cargo update -p Simple-Wayland-HotKey-Daemon --precise 1.2.0

Affected Products

1 product · 1 configurations
Application
swhkdwaycrate
1 version
1.1.5
Exploits & PoCs
1

Research 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 dependency
  1. Detect

    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.

  2. 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-27816 is resolved across your whole dependency graph.

  3. 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

SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data loss or a denial of service. A patch is available on the `1.1.0` branch of the repository.
O3 Security · Impact-Aware SCA

Is CVE-2022-27816 in your dependencies?

Find it across crates.io, including transitive dependencies.

CVE-2022-27816: Simple-Wayland-HotKey — Fixed in 1.2.0