OESA-2026-4934: cockpit security update
Cockpit makes GNU/Linux discoverable. See Linux server in a web browser and perform system tasks with a mouse. It’s easy to start containers, administer storage, configure networks, and inspect logs with this package. Security Fix(es):
A flaw was found in Cockpit. This vulnerability allows a remote attacker, without prior authentication, to send specially crafted fragmented WebSocket messages. These messages accumulate without a total-size limit, leading to unbounded memory exhaustion and a denial of service in the cockpit-ws service.(CVE-2026-91150)
A flaw was found in Cockpit. A local authenticated user with control over a target account's home directory can exploit a privileged symlink dereference vulnerability in the ssh-add-public-key.sh helper. When this helper runs with elevated privileges, it can be tricked into following attacker-controlled symlinks within the .ssh or authorizedkeys paths. This allows the attacker to arbitrarily change file ownership and modes, potentially leading to local privilege escalation and impacting the integrity, confidentiality, and availability of the system.(CVE-2026-91151)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/cockpitto a version that resolves this vulnerability.Fixed in 309-14.oe2403sp4
Event History
Frequently Asked Questions
Who can exploit the WebSocket memory-exhaustion issue?
A remote attacker does not need prior authentication. Exploitation requires sending specially crafted fragmented WebSocket messages to the cockpit-ws service.
What is the likely operational impact of the remote issue?
The crafted messages can accumulate without a total-size limit and exhaust memory in cockpit-ws. This can cause a denial of service.
What access is required for the local symlink issue?
An attacker must be a locally authenticated user and control the target account's home directory. The ssh-add-public-key.sh helper must run with elevated privileges for the attacker-controlled symlinks to be followed.
What can the local issue allow an attacker to do?
The attacker may arbitrarily change file ownership and modes through symlinks in .ssh or authorized_keys paths. This can potentially lead to local privilege escalation and affect system integrity, confidentiality, and availability.