OESA-2026-4934: cockpit security update

Published Nov 19, 2026
·
Updated

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

1 affected componentFixes available
openeuler/cockpit<309-14.oe2403sp4
309-14.oe2403sp4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/cockpit to a version that resolves this vulnerability.

    Fixed in 309-14.oe2403sp4

Event History

Nov 19, 2026
Advisory Published
via OSV·01:43 AM
Data Sourced
via OSV·01:43 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203