This page lists publicly disclosed CVE vulnerabilities affecting freedesktop libinput (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-50292 | In libinput before 1.30.4 and 1.31.x before 1.31.3, libinput-device-group unescaped phys output can inject udev properties leading to arbitrary root code execution | [email protected] | 7.4 | 0.05% | 2026-06-04 | 2026-06-05 |
| CVE-2026-35094 | A flaw was found in libinput. An attacker capable of deploying a Lua plugin file in specific system directories can exploit a dangling pointer vulnerability. This occurs when a garbage collection cleanup function is called, leaving a pointer that can then be printed to system logs. This could potentially expose sensitive data if the memory location is re-used, leading to information disclosure. For this exploit to work, Lua plugins must be enabled in libinput and loaded by the compositor. | [email protected] | 3.3 | 0.01% | 2026-04-01 | 2026-04-07 |
| CVE-2026-35093 | A flaw was found in libinput. A local attacker who can place a specially crafted Lua bytecode file in certain system or user configuration directories can bypass security restrictions. This allows the attacker to run unauthorized code with the same permissions as the program using libinput, such as a graphical compositor. This could lead to the attacker monitoring keyboard input and sending that information to an external location. | [email protected] | 8.8 | 0.01% | 2026-04-01 | 2026-04-07 |
| CVE-2022-1215 | A format string vulnerability was found in libinput | [email protected] | 7.8 | 0.04% | 2022-06-02 | 2024-11-21 |