Red Hat Security Advisory: cockpit-files security update
🔗 CVE IDs covered (3)
📋 Description
CVE-2026-91202 — cockpit-files: cockpit-files: Arbitrary file ownership change via symlink following in privileged paste CVE-2026-91203 — cockpit-files: cockpit-files: Arbitrary file ownership and permission modification via symlink race condition CVE-2026-91205 — cockpit-files: cockpit-files: Local attacker can hijack file ownership via symlink race
🎯 Affected products3
- Red Hat Enterprise Linux AppStream (v. 10)
- cockpit-files-0:43.1-1.el10_3.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10)
- cockpit-files-0:43.1-1.el10_3.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: A workaround is available for this issue: avoid using the privileged "Paste as owner" option in cockpit-files when pasting copied directory trees that may contain symlinks. If a privileged paste is required, keep the owner selection at "original", which skips the recursive chown code path entirely and prevents ownership changes from following symlinks to files outside the pasted directory. Once updated cockpit-files packages containing the fix are available for the affected streams, installing them resolves the issue. Workaround: Until a fixed package is available, avoid performing privileged ownership or permission changes through the Cockpit Files application in directories that are writable by untrusted or low-privileged users. Where possible, restrict or disable superuser-backed file operations (the elevated chown/chmod flows used for file creation, upload, ownership, and permission changes) for shared writable paths, and perform file metadata changes only on trusted directories. Exploitability is substantially reduced when privileged Cockpit sessions do not operate on attacker-writable directories. Workaround: Avoid using the privileged owner-assignment directory-creation flow in Cockpit Files inside directories that are writable by untrusted local users. Restrict write permissions on shared parent directories, and where directories must remain shared and writable, apply the sticky bit so users cannot replace directory entries they do not own. Creating directories without an owner assignment does not trigger the vulnerable privileged chown path and can be used where the owner-setting feature is not required. Updated packages that address this flaw are being delivered for the actively maintained releases.
🔗 References (6)
- selfhttps://access.redhat.com/errata/RHSA-2026:98566
- externalhttps://access.redhat.com/security/updates/classification/#moderate
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2465632
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2465834
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2466442
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_98566.json