Red Hat Updates Cockpit Files on RHEL 9

P2 — VALIDATE AND UPDATEMedium · 6.0 / 6.1 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Red Hat published RHSA-2026:84595 for cockpit-files on RHEL 9. The supported package addresses two Cockpit Files vulnerabilities involving file operations. Match each entitled system to the exact advisory relationship, apply cockpit-files 36.1-1.el9_8.1, validate dependent operations, and retain evidence.

Match The Entitled RHEL Stream And Apply Its Supported Package

What to do now: Inventory cockpit-files on RHEL 9, compare installed NEVRAs and entitlements with the exact Red Hat product relationships, apply cockpit-files 36.1-1.el9_8.1, validate dependent workloads, and preserve change evidence.

Open the authoritative advisory

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

Scope And Authority

Product scopecockpit-files on RHEL 9
AdvisoryRHSA-2026:84595
CVEsCVE-2026-91202, CVE-2026-91205
Authoritative release date2026-10-19 03:59:00 UTC
Authority revision date2026-10-19 04:00:52 UTC
Affected versionsThe RHEL 9 cockpit-files product relationship listed by RHSA-2026:84595.
Fixed versioncockpit-files 36.1-1.el9_8.1
CVSS base score6.0 / 6.1 (CVSS v3.1)
CVSS severityMedium
Exploitation statusNot stated by Red Hat; no exploitation claim is inferred.

What Changed

The supported package addresses two Cockpit Files vulnerabilities involving file operations.

What To Validate Now

  1. Inventory. Locate cockpit-files on RHEL 9; record the installed NEVRA, RHEL minor stream, repository and entitlement, accountable owner, exposure, dependent workloads, and maintenance group.
  2. Establish applicability. Use the product-status relationships in RHSA-2026:84595. The RHEL 9 cockpit-files product relationship listed by RHSA-2026:84595. Do not transfer package applicability between RHEL branches.
  3. Remediate. Install cockpit-files 36.1-1.el9_8.1 from the supported Red Hat repository for the matching entitled branch, following the current advisory and local change controls.
  4. Validate. Confirm the installed NEVRA and repository, restart affected services when required, exercise representative workloads 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

Use the exact supported package for each entitled RHEL stream. Test dependent applications and rollback before broad deployment; the advisory severity does not establish exploitation or applicability to a particular system.

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.