Ubuntu USN-8862-1 Fixes libXpm Vulnerability

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Ubuntu USN-8862-1 fixes excessive-resource use when libXpm processes zero-dimension XPM images. Canonical describes a local attacker causing denial of service. Update installed libxpm4 and xpmutils as applicable on the three listed releases; libxpm names the source package.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory libXpm vulnerability on Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-10-01 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopelibXpm vulnerability on Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy)
AdvisoryUSN-8862-1
CVECVE-2026-94287
Authoritative release date2026-10-01 12:51:01.382040 UTC
Authority revision dateNo separate material revision date is stated by Ubuntu; verified against the first-party notice API.
Affected versionsThe Ubuntu releases and source packages enumerated in USN-8862-1: Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy).
Fixed source build (not an install command)jammy: libxpm 1:3.5.12-1ubuntu0.22.04.4 / noble: libxpm 1:3.5.17-1ubuntu0.24.04.2 / resolute: libxpm 1:3.5.17-1ubuntu0.26.04.2
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

The defect is in handling XPM image dimensions. Identify applications and conversion jobs that use the library, including workloads that accept untrusted image files. The notice does not establish remote code execution or active exploitation.

Fixed Binary Packages

Canonical's notice API lists these visible binary fixes. Match installed packages; this is not an instruction to install every listed package.

  • jammy: libxpm4 1:3.5.12-1ubuntu0.22.04.4; xpmutils 1:3.5.12-1ubuntu0.22.04.4.
  • noble: libxpm4 1:3.5.17-1ubuntu0.24.04.2; xpmutils 1:3.5.17-1ubuntu0.24.04.2.
  • resolute: libxpm4 1:3.5.17-1ubuntu0.26.04.2; xpmutils 1:3.5.17-1ubuntu0.26.04.2.

What To Validate Now

  1. Inventory. Locate libXpm vulnerability on Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy) deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Match the installed Ubuntu release and binary packages to USN-8862-1. The source build identifies packaging provenance; it is not necessarily an installable package name. Do not transfer a version from another release or assume bundled upstream software is covered.
  3. Remediate. Update the installed affected binary packages through the supported Ubuntu security or applicable Pro/ESM repository for that release. Use the USN package table, not the source-package name as an installation command. Keep the Ubuntu version epoch and suffix when checking the fixed build.
  4. Validate. Confirm the correct installed binary builds and restart affected long-running consumers when required. Open or convert a benign representative image and check normal resource use. Do not submit a malicious image to production to prove patching.
  5. 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

The retrieved notice lists jammy, noble and resolute security-pocket fixes. Preserve the full Ubuntu version including the epoch. Independently packaged image software may include its own library and requires separate applicability review.

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.