Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

CVSS 3.1 6.0 MEDIUMCheck source for fixed versionsKEV status unknown

cve-program · CVE-2026-91205

Published

A flaw was found in cockpit-files. A local unprivileged attacker can exploit a race condition during directory creation with owner assignment. By controlling a writable parent directory, the attacker can replace a newly created directory with a symbolic link (symlink) before the ownership change operation (chown) is applied. This allows the attacker to redirect the ownership change to an arbitrary file, potentially leading to information disclosure or unauthorized modification of sensitive files.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

5 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

11 Nov 2026 13:57:25 UTC

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

cve-program · CVE-2026-91205 · Published

11 Nov 2026 12:57:25 UTC

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

cve-program · CVE-2026-91205 · Published

6 Nov 2026 06:36:20 UTC

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

cve-program · CVE-2026-91205 · Published

6 Nov 2026 02:36:20 UTC

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

cve-program · CVE-2026-91205 · Published

23 Oct 2026 15:48:27 UTC

Cockpit-files: cockpit-files: local attacker can hijack file ownership via symlink race

cve-program · CVE-2026-91205 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 13:16 UTC · 255 of 275 readable · 250 fully read · documentation 469/469 current