How severe is GHSA-8m49-2xj8-67v9?

GHSA-8m49-2xj8-67v9 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8m49-2xj8-67v9?

GHSA-8m49-2xj8-67v9 affects the following packages: Simple-Wayland-HotKey-Daemon (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8m49-2xj8-67v9?

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-8m49-2xj8-67v9 is resolved across your whole dependency graph.

How do I detect GHSA-8m49-2xj8-67v9 in my crates.io dependencies?

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.

How do I mitigate GHSA-8m49-2xj8-67v9 if there is no patch (or I can't update yet)?

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.

Is GHSA-8m49-2xj8-67v9 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-8m49-2xj8-67v9, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-8m49-2xj8-67v9?

GHSA-8m49-2xj8-67v9 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8m49-2xj8-67v9?

GHSA-8m49-2xj8-67v9 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8m49-2xj8-67v9 published, and has it been updated?

GHSA-8m49-2xj8-67v9 was published on March 31, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

GHSA-8m49-2xj8-67v9 — Simple-Wayland-HotKey-Dae…

HIGHFix: waycrate/swhkd@0b620a0

GHSA-8m49-2xj8-67v9 is a high-severity (CVSS 7.1) CWE-59 vulnerability in Simple-Wayland-HotKey-Daemon. 1 public exploit reference exists, 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 asCVE-2022-27816

Published

Mar 31, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 26, 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 CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-8m49-2xj8-67v9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`Simple-Wayland-HotKey-Daemon`	all versions	1.2.0`cargo 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

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data…

openwall.comNVDApr 2022

Detection & mitigation playbook

Open-source dependency

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.
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-8m49-2xj8-67v9 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

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 GHSA-8m49-2xj8-67v9 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.1/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

CWE Classification

CWE-59CWE-59

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Mar 31, 2022

First exploit

Apr 27, 2022

Last updated

Nov 8, 2023

Identifiers

GHSA-8m49-2xj8-67v9

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webopenwall.com Packagegithub.com

Related vulnerabilities

Also affects Simple-Wayland-HotKey-Daemon

This CVE is high severity; 3 of 6 other CVEs affecting Simple-Wayland-HotKey-Daemon are rated as high or higher (top: critical).

CVE-2022-27817CVE-2022-27814CVE-2022-27819CVE-2022-27818CVE-2022-27816CVE-2022-27815

Same weakness: CWE-59

This CVE is high severity; 1 of 2 other CVEs with CWE-59 is rated as high or higher (top: high).

CVE-2026-85731CVE-2026-88016Browse all CWE-59

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023