CVE-2026-91202 — Cockpit-files: cockpit-files: arbitrary file ownership change via symlink following in privileged paste

A flaw was found in cockpit-files. A low-privileged local user can exploit this vulnerability by crafting a directory containing a symbolic link (symlink) and then using the privileged "Paste as owner" function. This allows for arbitrary file ownership changes outside the intended pasted directory, leading to a compromise of data integrity. In some cases, this could also lead to reduced confidentiality if the new ownership grants unauthorized read access. Exploitation requires user interaction to select a non-original owner during the paste operation.

Published Sep 18, 2026Updated Sep 18, 2026Sources: cvelistV5, redhat

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

Not scored

FIRST has not published a score

Affects

redhat

2 products listed

CVSS base

6.1

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

redhat

Products (2)

red hat enterprise linux 10red hat enterprise linux 9

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.1	CVSS 3.1	MEDIUM	—	—	cvelistV5

Weakness & attack patterns

CWE-61

References

2 on the record

access.redhat.com/security/cve/CVE-2026-91202
vdb-entry, x_refsource_REDHAT
bugzilla.redhat.com/show_bug.cgi?id=2465834
issue-tracking, x_refsource_REDHAT

Elsewhere on this site

redhatevery CVE for this vendor
CWE-61other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.