Ubuntu USN-8787-1 Fixes libxml2 Vulnerabilities
Tech GuruQuick Answer
Ubuntu's USN-8787-1 updates libxml2 across the seven release streams listed below. CVE-2026-86140 can cause a crash or code execution through certain XML elements; CVE-2026-74860 concerns crashes when processing XML through Python bindings. Match the host release and the actual library or binding packages before updating.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory libxml2 consumers and Python bindings, identify untrusted XML input paths, apply the corresponding Ubuntu packages, and verify the active application libraries and supported activation steps.
Last verified: 2026-09-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | libxml2 vulnerabilities on 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) |
|---|---|
| Advisory | USN-8787-1 |
| CVEs | CVE-2026-74860, CVE-2026-86140 |
| Authoritative release date | 2026-09-21 12:31:10.750566 UTC |
| Authority revision date | 2026-09-21 12:31:10.750566 UTC |
| Affected versions | The Ubuntu releases and packages enumerated in USN-8787-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: libxml2 2.9.4+dfsg1-6.1ubuntu1.9+esm8 / focal: libxml2 2.9.10+dfsg-5ubuntu0.20.04.10+esm5 / jammy: libxml2 2.9.13+dfsg-1ubuntu0.13 / noble: libxml2 2.9.14+dfsg-1.3ubuntu3.9 / resolute: libxml2 2.15.2+dfsg-0.1ubuntu0.2 / trusty: libxml2 2.9.1+dfsg1-3ubuntu4.13+esm12 / xenial: libxml2 2.9.3+dfsg1-1ubuntu0.7+esm13 |
| 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
The two CVEs do not have identical scope: 86140 concerns XML-element handling with possible code execution, while 74860 concerns denial of service through Python bindings. Ubuntu's instructions say a standard update generally makes the necessary changes. The fixed-version table uses source-package names; on resolute, the runtime library is libxml2-16, and installed Python bindings or tools also need the applicable packages.
What To Validate Now
- Inventory. Record the Ubuntu release, runtime libxml2 package, installed Python bindings and tools, and applications that process external XML.
- Establish applicability. Compare each deployment with the authority's affected-version statement: The Ubuntu releases and packages enumerated in USN-8787-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. Use the fixed version for the host's release in the table, with the corresponding runtime and binding packages from Ubuntu's advisory. Do not replace an ESM or another release's package with a numerically higher build from a different distribution stream.
- Validate. Confirm the deployed library and binding versions, follow supported activation requirements, and test approved XML parsing through each application and Python integration actually used.
- 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
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
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.
