CVE-2026-50265 is a local privilege escalation vulnerability in libinput's udev helper, libinput-device-group. The helper incorporates a device's phys sysattr into a udev property value and prints it as a KEY=VALUE pair that udev imports into its environment. Because newline characters in the phys sysattr were not escaped or sanitized, a malicious uinput or uhid device could supply a phys value containing '\n', causing udev to parse the helper output as multiple KEY=VALUE pairs instead of a single property. This enables injection of unintended udev properties. The advisory notes that dangerous properties such as REMOVE_CMD can be injected, resulting in arbitrary command execution as root. The issue affects libinput versions up to 1.31.2 and 1.30.3 and was fixed in 1.31.3 and 1.30.4. The CVE record indicates this ID was later rejected as a duplicate of CVE-2026-50292, but both refer to the same underlying vulnerability.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.