Ubuntu USN-8845-1 Fixes GVfs Vulnerabilities

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

Quick Answer

The authority published USN-8845-1 for GVfs 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). Several security issues were fixed in GVfs. After a standard system update you need to restart your session to make all the necessary changes. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory GVfs 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), 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 scopeGVfs 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)
AdvisoryUSN-8845-1
CVEsCVE-2026-84268, CVE-2026-88924
Authoritative release date2026-09-30 15:54:56.826327 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-8845-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).
Fixed versionbionic: gvfs 1.36.1-0ubuntu1.3.3+esm1 / focal: gvfs 1.44.1-1ubuntu1.2+esm1 / jammy: gvfs 1.48.2-0ubuntu1.2 / noble: gvfs 1.54.4-0ubuntu1~24.04.4 / resolute: gvfs 1.60.0-1ubuntu0.1 / xenial: gvfs 1.28.2-1ubuntu1~16.04.3+esm1
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

Several security issues were fixed in GVfs. After a standard system update you need to restart your session to make all the necessary changes.

What To Validate Now

  1. Inventory. Locate GVfs 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) deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare installed source packages and Ubuntu releases with USN-8845-1. Do not infer scope for another release, an upstream build, or a similarly named binary package.
  3. Remediate. Install the notice's exact fixed source-package build through the supported Ubuntu security or ESM channel for the matching release, following current Ubuntu instructions and change control.
  4. Validate. Confirm the resulting source-package version, restart or reload affected services when Ubuntu tooling requires it, exercise representative workflows and recovery paths, monitor for regressions, and document exceptions.
  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

Some listed fixes are delivered through Ubuntu Pro or ESM. Confirm entitlement and repository state, use the exact supported release stream, and test dependencies and rollback. Severity alone 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.