CVE-2022-26530
CVE-2022-26530 is a critical-severity vulnerability in Swaywm Swaylock with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: Critical (CVSS 3.x base score 9.1)
- CVSS v2: 6.4
- EPSS exploit prediction: 1% (71st percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Swaywm Swaylock
- Published:
- Last modified:
Description
swaylock before 1.6 allows attackers to trigger a crash and achieve unlocked access to a Wayland compositor.
Frequently asked questions
- What is CVE-2022-26530?
- swaylock before 1.6 allows attackers to trigger a crash and achieve unlocked access to a Wayland compositor.
- How severe is CVE-2022-26530?
- CVE-2022-26530 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
- Is CVE-2022-26530 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-26530?
- CVE-2022-26530 affects Swaywm Swaylock. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-26530?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2022-26530 published?
- CVE-2022-26530 was published on 2022-04-03 and last updated on 2026-06-17.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2066596
- https://github.com/swaywm/swaylock/commit/1d1c75b6316d21933069a9d201f966d84099f6ca
- https://github.com/swaywm/swaylock/pull/219
Affected products (1)
- cpe:2.3:a:swaywm:swaylock:*:*:*:*:*:*:*:*