CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (7.5) in x.org libxi. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2026-109090 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109090?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109090?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109090 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| x.org libXi | before 1.8.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | libxi | no fix listed | DEBIAN-CVE-2026-109090 |
| Debian | 14 | libxi | 2:1.8.4-1 | DEBIAN-CVE-2026-109090 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 4 more | libxi | no fix listed | UBUNTU-CVE-2026-109090 |
| Red Hat | enterprise_linux:8::appstream | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.7.10-4.el8_10 | RHSA-2026:93438 |
| Red Hat | enterprise_linux:9::appstream | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.7.10-8.el9_8.3 | RHSA-2026:93439 |
| Red Hat | enterprise_linux:9::appstream | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.7.10-8.el9_9.3 | RHSA-2026:98504 |
| Red Hat | enterprise_linux:10.2 | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.8.1-7.el10_2.3 | RHSA-2026:93441 |
| Red Hat | enterprise_linux:10.3 | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.8.1-7.el10_3.3 | RHSA-2026:98611 |
| Red Hat | hummingbird:1 | libXi, libXi-devel | 0:1.8.4-1.hum1 | RHSA-2026:86772 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 11 more | libXi | 1.7.9-150000.3.7.1 | SUSE-SU-2026:5165-1 |
| SUSE | Linux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5 | libXi | 1.7.4-18.11.1 | SUSE-SU-2026:5166-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | libXi | 1.8.2-160000.5.1 | SUSE-SU-2026:24726-1 |
| SUSE | Linux Micro 6.0 | libXi | 1.8.1-159998.1.1 | SUSE-SU-2026:24366-1 |
| openSUSE | Tumbleweed | libXi | 1.8.3-3.1 | openSUSE-SU-2026:12154-1 |
| AlmaLinux | 8 | libXi, libXi-devel | 1.7.10-4.el8_10 | ALSA-2026:93438 |
| AlmaLinux | 9 | libXi, libXi-devel | 1.7.10-8.el9_8.3 | ALSA-2026:93439 |
| AlmaLinux | 9 | libXi, libXi-devel | 1.7.10-8.el9_9.3 | ALSA-2026:98504 |
| AlmaLinux | 10 | libXi, libXi-devel | 1.8.1-7.el10_2.3 | ALSA-2026:93441 |
| AlmaLinux | 10 | libXi, libXi-devel | 1.8.1-7.el10_3.3 | ALSA-2026:98611 |
| Rocky Linux | 8 | libXi | 0:1.7.10-4.el8_10 | RLSA-2026:93438 |
| Rocky Linux | 9 | libXi | 0:1.7.10-8.el9_8.3 | RLSA-2026:93439 RLSA-2026:98504 |
| Rocky Linux | 10 | libXi | 0:1.8.1-7.el10_2.3 | RLSA-2026:93441 |
| Rocky Linux | 10 | libXi, libXi-devel, libXi-debuginfo and 1 more | 0:1.8.1-7.el10_2.3 | RLSA-2026:98611 |
| Alpine | v3.24 | libxi | 1.8.4-r0 | ALPINE-CVE-2026-109090 |
| Azure Linux | 3 | libXi | 1.8.4-1 | AZL-111169 |
| Alpaquita | 23, 25, stream | libxi | 1.8.4-r0 | BELL-CVE-2026-109090 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.
Red Hat rates this Important.
This vulnerability is rated as Important severity because successful exploitation allows an untrusted display service to execute code with the permissions of the connecting user process or induce an immediate application crash. In standard Red Hat Enterprise Linux environments, desktop and terminal applications interact solely with trusted, locally managed X11 or Xwayland display servers, which substantially limits practical attack exposure. The elevated risk is primarily present when client programs are configured to communicate with remote or unverified display servers across a network.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to properly size the allocation for XDeviceEnableState and validate wire length before parsing DEVICE_ENABLE replies in libXi's XGetDeviceControl: upgrade to libXi 1.8.4 (or the fixed Libxi builds), which add a DEVICE_ENABLE case arm in XGetDCtl.c to allocate sizeof(XDeviceEnableState) and validate wire bytes against sizeof(xDeviceEnableState), closing crafted X11 DEVICE_ENABLE reply. Until patched, this is a concern on Linux systems running X11 client applications connecting to remote or unverified X display servers, so Restrict client applications from connecting to remote or unverified display servers across the network, ensuring connections are limited to trusted, locally managed X11 or Xwayland instances. As a compensating measure, Enable Address Space Layout Randomization to randomize process memory layout and hinder reliable code execution, Compile client binaries with Full RELRO and PIE to make relocation tables read-only and randomize code segments, Implement Control Flow Integrity or Shadow Call Stack to restrict indirect call and jump targets, Enable FORTIFY_SOURCE buffer overflow detection to abort execution upon detecting heap buffer overruns, Run SELinux in enforcing mode to confine the X11 client application within a mandatory access control domain, and Isolate client applications using Linux user, PID, network, and mount namespaces to restrict host access. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap-based buffer overflow — apply the upstream patch to fully remediate.
Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | libXi-0:1.8.1-7.el10_2.3 | Fixed 2026-11-02 | RHSA-2026:93441 |
| Red Hat Enterprise Linux 8 | libXi-0:1.7.10-4.el8_10 | Fixed 2026-11-02 | RHSA-2026:93438 |
| Red Hat Enterprise Linux 9 | libXi-0:1.7.10-8.el9_8.3 | Fixed 2026-11-02 | RHSA-2026:93439 |
| Red Hat Hardened Images | libxi-main-1.8.4-1.hum1 | Fixed 2026-10-21 | RHSA-2026:86772 |
| Red Hat Enterprise Linux 6 | libXi | Not affected | |
| Red Hat Enterprise Linux 7 | libXi | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-109090.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.