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

Insecure temporary file usage in SWHKDGHSA-r3r5-jhw6-4634

CRITICALFix: waycrate/swhkd@f70b99d

GHSA-r3r5-jhw6-4634 is a critical-severity (CVSS 9.1) CWE-668 vulnerability in Simple-Wayland-HotKey-Daemon. A fix is available for Simple-Wayland-HotKey-Daemon — see the affected versions and patch details below.

Also known asCVE-2022-27818
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.00%0.77%1.54%2.31%0.5%1.8%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/swhkd.sock pathname. There can be an information leak or denial of service.

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

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 GHSA-r3r5-jhw6-4634 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/swhkd.sock pathname. There can be an information leak or denial of service.
O3 Security · Impact-Aware SCA

Is GHSA-r3r5-jhw6-4634 in your dependencies?

Find it across crates.io, including transitive dependencies.

Insecure temporary file usage in SWHKD (Critical 9.1)