Skip to content

← Actionable
Medium, CVSS 4.4

Exposure of Resource to Wrong Sphere in Simple-Wayland-HotKey-Daemon

CVE-2022-27817GHSA-h5wh-7h2j-h999

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • crates.io Simple-Wayland-HotKey-Daemon

    Affected
    <= 1.1.5
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.4 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
EPSS
  • CVE-2022-27817: 0.45% estimated exploitation activity in the next 30 days; percentile 39.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

SWHKD 1.1.5 consumes the keyboard events of unintended users. This could potentially cause an information leak, but is usually a denial of functionality.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-h5wh-7h2j-h999

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-27817

Advisory: Exposure of Resource to Wrong Sphere in Simple-Wayland-HotKey-Daemon
IDs: CVE-2022-27817, GHSA-h5wh-7h2j-h999
Record: https://patchnext.com/advisories/cve-2022-27817 (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io Simple-Wayland-HotKey-Daemon: affected <= 1.1.5

## Suggested inspection (read-only)
- crates.io Simple-Wayland-HotKey-Daemon: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on Simple-Wayland-HotKey-Daemon.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h5wh-7h2j-h999 (GitHub-reviewed advisory GHSA-h5wh-7h2j-h999 lists affected ranges: crates.io Simple-Wayland-HotKey-Daemon >=0 <=1.1.5)

Commands are suggestions: review each one before running it.

Loading voting…