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-109089 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109089?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109089?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-109089 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-109089 |
| Debian | 14 | libxi | 2:1.8.4-1 | DEBIAN-CVE-2026-109089 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 4 more | libxi | no fix listed | UBUNTU-CVE-2026-109089 |
| 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-109089 |
| Azure Linux | 3 | libXi | 1.8.4-1 | AZL-111166 |
| Alpaquita | 23, 25, stream | libxi | 1.8.4-r0 | BELL-CVE-2026-109089 |
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 because malicious responses from an X server could cause memory corruption, potentially allowing arbitrary code execution within the privileges of the client application. On Red Hat Enterprise Linux systems, graphical applications typically communicate only with trusted, local display servers managed by the OS. Exploiting this condition requires a user or client program to explicitly connect to an untrusted or compromised external display server, which limits exposure in standard operational configurations.
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-03) ---
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 restrict graphical client applications from connecting to untrusted external X display servers to prevent malformed device control replies from reaching libXi: upgrade to libXi 1.8.4+ (or the fixed Libxi builds), which validate that the reply control matches the requested control and immediately jump to an exit path if they differ, closing all 2 injection vectors (mismatched DEVICE_RESOLUTION reply control values, crafted X server responses). Until patched, this is a concern on Linux client applications linked against libXi that issue XGetDeviceControl requests, so Prevent client applications from establishing connections to untrusted or external display servers, ensuring X11 traffic is restricted strictly to trusted local display servers managed by the OS. As a compensating measure, Enable Address Space Layout Randomization to randomize userspace memory addresses and impede shellcode execution or ROP gadget chaining, Enable Full RELRO and PIE to make the Global Offset Table read-only and randomize binary code pages against GOT overwrite techniques, Enable Control Flow Integrity or Shadow Call Stack to validate indirect branch targets and return addresses against control flow hijacking, and Enforce SELinux to confine the compromised client process to its domain and restrict access to system resources. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap buffer overflow defect — 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-109089.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.