Root code execution via newline property injection
Published Jun 5, 2026 · Updated Jun 5, 2026
CRLF injection in libinput-device-group allows local users to execute code as root through crafted uinput or uhid device metadata. The helper prints an unescaped phys sysattr as KEY=VALUE data, so an embedded newline creates a second udev property such as REMOVE_CMD. The supplied identifier is rejected as a duplicate of CVE-2026-50292; exploitation requires access to /dev/uinput or /dev/uhid, which is normally root-restricted.
Summary
What happened
CRLF injection in libinput-device-group allows local users to execute code as root through crafted uinput or uhid device metadata. The helper prints an unescaped phys sysattr as KEY=VALUE data, so an embedded newline creates a second udev property such as REMOVE_CMD. The supplied identifier is rejected as a duplicate of CVE-2026-50292; exploitation requires access to /dev/uinput or /dev/uhid, which is normally root-restricted.
The record
- CVE
- CVE-2026-50265
- Published
- Jun 5, 2026
- Updated
- Jun 5, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-93, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 5, 2026CVE publishedPublication date reported by the CVE source.
- Jun 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo