CVE-2022-26530

Description

swaylock before 1.6 allows attackers to trigger a crash and achieve unlocked access to a Wayland compositor.

9.1

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.53%

Third-Party Advisory redhat.com Third-Party Advisory github.com Third-Party Advisory github.com

Affected: n/a n/a

References

Link	Tags
https://github.com/swaywm/swaylock/pull/219	issue tracking third party advisory patch
https://github.com/swaywm/swaylock/commit/1d1c75b6316d21933069a9d201f966d84099f6ca	third party advisory patch
https://bugzilla.redhat.com/show_bug.cgi?id=2066596	issue tracking third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-26530?: CVE-2022-26530 has been scored as a critical severity vulnerability.
How to fix CVE-2022-26530?: To fix CVE-2022-26530, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-26530 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2022-26530 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.