Ubuntu libX11 Updates Address Four Vulnerabilities
Quick Answer
Canonical published USN-8913-1 for libx11 on supported Ubuntu LTS and ESM releases. Match each host to the listed Ubuntu release and source package, apply the exact archive update, validate dependent workflows, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory libx11 on supported Ubuntu LTS and ESM releases, match the exact release-package rows in USN-8913-1, install the Canonical-provided package versions, restart affected processes or instances where required, and validate representative operations.
Last verified: 2026-10-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | libx11 on supported Ubuntu LTS and ESM releases |
|---|---|
| Advisory | USN-8913-1 |
| CVEs | CVE-2026-88806, CVE-2026-94283, CVE-2026-94284, CVE-2026-94285 |
| Authoritative release date | 2026-10-12 12:53:41.071205 UTC |
| Authority revision date | 2026-10-12 12:53:41.071205 UTC |
| Affected versions | The Ubuntu releases and source packages enumerated by USN-8913-1: Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic), Ubuntu 16.04 ESM (xenial), Ubuntu 14.04 ESM (trusty). |
| Fixed version | bionic: libx11 2:1.6.4-3ubuntu0.4+esm3 / focal: libx11 2:1.6.9-2ubuntu1.6+esm1 / jammy: libx11 2:1.7.5-1ubuntu0.4 / noble: libx11 2:1.8.7-1ubuntu0.1 / resolute: libx11 2:1.8.13-1ubuntu0.1 / trusty: libx11 2:1.6.2-1ubuntu2.1+esm6 / xenial: libx11 2:1.6.3-1ubuntu2.2+esm5 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Ubuntu addressed malformed XKB replies, XIM processing, and multibyte conversion paths that could lead to denial of service or, for CVE-2026-88806, code execution when a user connects to a malicious X server.
What To Validate Now
- Inventory. Locate libx11 on supported Ubuntu LTS and ESM releases deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: The Ubuntu releases and source packages enumerated by USN-8913-1: Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic), Ubuntu 16.04 ESM (xenial), Ubuntu 14.04 ESM (trusty). Do not infer applicability from product family or severity alone.
- Remediate. Apply bionic: libx11 2:1.6.4-3ubuntu0.4+esm3 / focal: libx11 2:1.6.9-2ubuntu1.6+esm1 / jammy: libx11 2:1.7.5-1ubuntu0.4 / noble: libx11 2:1.8.7-1ubuntu0.1 / resolute: libx11 2:1.8.13-1ubuntu0.1 / trusty: libx11 2:1.6.2-1ubuntu2.1+esm6 / xenial: libx11 2:1.6.3-1ubuntu2.2+esm5 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Prioritize workstations and application hosts that connect to remote or less-trusted X servers. Test desktop sessions, X forwarding, kiosk workflows, and dependent applications after updating. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

