# CVE-2026-50292: Code injection in libinput

> Attackers can inject udev properties via unescaped phys output in libinput, leading to arbitrary root code execution on Linux systems.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** ALSA-2026:39296, AZL-89378, CLSA-2026-1783709526, CLSA-2026-1784017931, CLSA-2026-1784020479, CLSA-2026-1792170117, CLSA-2026-1792174065, CVE-2026-50265, DEBIAN-CVE-2026-50292, GHSA-jcq8-v68h-2c44, MGASA-2026-0208, OESA-2026-2628, RHSA-2026:39296, RHSA-2026:43290, RLSA-2026:39296, UBUNTU-CVE-2026-50292, USN-8602-1, USN-8753-1

## What is CVE-2026-50292?

CVE-2026-50292 is a high-severity code injection vulnerability in freedesktop libinput, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-50292?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libinput` | AlmaLinux:10 | All versions | 1.30.1-2.el10_2 |
| `libinput-devel` | AlmaLinux:10 | All versions | 1.30.1-2.el10_2 |
| `libinput-utils` | AlmaLinux:10 | All versions | 1.30.1-2.el10_2 |
| `libinput` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-test-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-utils` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput-utils-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.30.1-2.el10_2 |
| `libinput` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-test-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-utils` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput-utils-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.26.1-5.el10_0.1 |
| `libinput` | Rocky Linux:10 | All versions | 0:1.30.1-2.el10_2 |

Products: Freedesktop Libinput.

## How do I fix CVE-2026-50292?

Upgrade to a fixed version.

## Is CVE-2026-50292 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50292 exists.

## Other vulnerabilities in freedesktop libinput

- [CVE-2022-1215](https://insights.sbomify.com/CVE-2022-1215/): Other in libinput (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50292 and fix it if it is affected.

What it is: CVE-2026-50292 is a high-severity code injection vulnerability in freedesktop libinput, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50292 exists.

Affected product: freedesktop libinput. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50292/ (Markdown: https://insights.sbomify.com/CVE-2026-50292/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50292
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50292
- OSV: https://osv.dev/vulnerability/CVE-2026-50292

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50292/
Summaries are generated and may contain mistakes; the official description above is the record.