dbcve.org
FedoraOperating system · Fedoraproject

CVE-2026-35093

HIGH · 8.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 1.30.3 / 1.31.1 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

libinput loads Lua bytecode configuration files from system or user directories. A local attacker who can write to these configuration directories can place malicious Lua bytecode that gets executed with the privileges of the libinput-using program (e.g., graphical compositor), enabling keyboard monitoring and exfiltration.

MitigationRestrict write permissions on libinput configuration directories to prevent unauthorized file placement; remove any untrusted Lua bytecode files from configuration locations; update libinput if a security patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 43= 44
LibinputApplication
Affected:< 1.30.3>= 1.30.4, < 1.31.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed libinput version
    Run 'libinput --version' or check your package manager (e.g., 'rpm -q libinput' on Fedora/RHEL, 'dpkg -l libinput' on Debian/Ubuntu)
    Affected if Version is < 1.30.3, OR >= 1.30.4 AND < 1.31.1, OR matches Fedora 43 or 44
  2. Locate libinput configuration directories
    Check for the presence of configuration directories: typically ~/.config/libinput/ (user) and /etc/libinput/ or /usr/share/libinput/ (system). Look for any .lua files in these locations
    Affected if Lua configuration files (.lua) exist in libinput configuration directories
  3. Inspect file permissions on configuration directories
    Run 'ls -la' on ~/.config/libinput/ and /etc/libinput/ (or /usr/share/libinput/) to verify write permissions. Check if directories are writable by non-root users
    Affected if Configuration directories or Lua files are writable by unprivileged users or groups
  4. Determine if libinput loads user configurations
    Review libinput documentation or test if libinput reads from user configuration paths during normal operation. Check compositor logs for libinput configuration loading
    Affected if Libinput is configured to load configuration files from user-writable paths

A system is affected if it runs a vulnerable libinput version AND has writable Lua configuration files in directories that libinput reads during operation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.30.3 / 1.31.1 or later
Fixed in 1.30.31.31.1
Interim mitigation

Restrict write permissions on libinput configuration directories to prevent unauthorized file placement; remove any untrusted Lua bytecode files from configuration locations; update libinput if a security patch is available.

Recommended fix High confidence

libinput >= 1.31.1; Fedora packages containing fixed libinput

  1. Identify the current libinput version installed (e.g., 'rpm -q libinput' or 'libinput --version')
  2. For Fedora systems: Run 'sudo dnf update libinput' to apply the latest available package
  3. Alternatively, manually upgrade libinput to version 1.31.1 or later from source: Download from https://gitlab.freedesktop.org/libinput/libinput/-/releases
  4. Verify the fix by checking 'libinput --version' shows version 1.31.1 or higher
  5. Ensure any programs using libinput (e.g., desktop compositors, display managers) are restarted to load the updated library
Caveat Minimal - this is a security patch; ensure display server restart after update to apply protection

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data