CVSS 3.1
6.0 mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NMedium (6.0) in red hat. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NExplain CVE-2026-91205 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-91205?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-91205?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-91205 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat Enterprise Linux 10 | 0:36.1-1.el10_2 |
| Red Hat Enterprise Linux 10 | 0:43.1-1.el10_3 |
| Red Hat Enterprise Linux 9 | 0:36.1-1.el9_8 |
| Red Hat Enterprise Linux 9 | 0:43.1-1.el9_9 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | cockpit-files | 45-1 | DEBIAN-CVE-2026-91205 |
| Ubuntu | 26.04:LTS, 26.10 | cockpit-files | no fix listed | UBUNTU-CVE-2026-91205 |
| Red Hat | enterprise_linux:9::appstream | cockpit-files | 0:36.1-1.el9_8 | RHSA-2026:84595 |
| Red Hat | enterprise_linux:9::appstream | cockpit-files | 0:43.1-1.el9_9 | RHSA-2026:98458 |
| Red Hat | enterprise_linux:10.2 | cockpit-files | 0:36.1-1.el10_2 | RHSA-2026:95570 |
| Red Hat | enterprise_linux:10.3 | cockpit-files | 0:43.1-1.el10_3 | RHSA-2026:98566 |
| AlmaLinux | 9 | cockpit-files | 36.1-1.el9_8 | ALSA-2026:84595 |
| AlmaLinux | 10 | cockpit-files | 36.1-1.el10_2 | ALSA-2026:95570 |
| Rocky Linux | 9 | cockpit-files | 0:36.1-1.el9_8 | RLSA-2026:84595 |
| Rocky Linux | 9 | cockpit-files | 0:43.1-1.el9_9 | RLSA-2026:98458 |
| Rocky Linux | 10 | cockpit-files | 0:36.1-1.el10_2 | RLSA-2026:95570 |
| Rocky Linux | 10 | cockpit-files | 0:43.1-1.el10_3 | RLSA-2026:98566 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Moderate.
A moderate severity symlink race condition was found in cockpit-files, which affects the cockpit-files package as shipped in Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS, and Fedora. When a user creates a directory with an owner assignment through Cockpit Files, the privileged directory creation (mkdir) and ownership change (chown) are performed as two separate operations on the same pathname. A local unprivileged attacker who can write to the parent directory can replace the newly created directory entry with a symlink in the window between the two operations, redirecting the privileged ownership change onto an arbitrary file of the attacker's choosing. If the race is won, ownership of sensitive files such as /etc/shadow can be transferred to the attacker, resulting in information disclosure or unauthorized modification of those files. Exploitation is materially constrained: it requires local access, an attacker-writable parent directory, user interaction to trigger the directory-creation flow with owner assignment, and winning the race window. This is reflected in the CVSS 3.1 score of 6.0 (AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N), which is consistent between Red Hat and the upstream CVE record. A fix is being pursued for the actively maintained Red Hat Enterprise Linux and Fedora releases. For the deferred streams (RHEL 9.6.z, RHEL 10.0.z, and the Red Hat In-Vehicle OS streams), the fix is deferred given the moderate severity and the practical difficulty of exploitation; the residual risk is limited to systems where untrusted local users have write access to directories used as parents for the privileged owner-assignment flow.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | cockpit-files-0:36.1-1.el10_2 | Fixed 2026-11-05 | RHSA-2026:95570 |
| Red Hat Enterprise Linux 10 | cockpit-files-0:43.1-1.el10_3 | Fixed 2026-11-11 | RHSA-2026:98566 |
| Red Hat Enterprise Linux 9 | cockpit-files-0:36.1-1.el9_8 | Fixed 2026-10-19 | RHSA-2026:84595 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-91205.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.