RHSA-2026:94533HighCVSS 7.5

Red Hat Security Advisory: cockpit security update

Published
November 3, 2026
Last Modified
November 6, 2026

🔗 CVE IDs covered (3)

CVE-2026-91149 →CVE-2026-76235 →CVE-2026-91147 →

📋 Description

CVE-2026-76235 — cockpit-ws: cockpit: cockpit-ws: unauthenticated remote memory leak via CockpitLang cookie in send_login_html CVE-2026-91147 — cockpit: Cockpit: Denial of Service in cockpit-ws due to URL-root handling without a trailing slash CVE-2026-91149 — cockpit: Cockpit: Denial of Service via unbounded connection thread spawning

🎯 Affected products28

  • Red Hat Enterprise Linux AppStream (v. 9)
  • Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-0:356.4-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-0:356.4-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-0:356.4-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-0:356.4-1.el9_8.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-0:356.4-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-bridge-0:356.4-1.el9_8.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debuginfo-0:356.4-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debuginfo-0:356.4-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debuginfo-0:356.4-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debuginfo-0:356.4-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debugsource-0:356.4-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debugsource-0:356.4-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debugsource-0:356.4-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-debugsource-0:356.4-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-doc-0:356.4-1.el9_8.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-packagekit-0:356.4-1.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • cockpit-storaged-0:356.4-1.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • cockpit-system-0:356.4-1.el9_8.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-0:356.4-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-0:356.4-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-0:356.4-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-0:356.4-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-selinux-0:356.4-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-selinux-0:356.4-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-selinux-0:356.4-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • cockpit-ws-selinux-0:356.4-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Restrict network access to the cockpit port to trusted clients until a fix is available. No configuration-level mitigation removes the flaw entirely, since the login page must remain reachable without authentication. Workaround: A code fix is being pursued for the affected streams. Until updated packages are available, avoid configuring a non-empty [WebService] UrlRoot in cockpit-ws where feasible. If a non-empty UrlRoot is required, configure the front-end proxy or TLS terminator in front of cockpit-ws to rewrite or redirect requests for the exact configured prefix (for example, /cockpit) to the trailing-slash form (for example, /cockpit/) before forwarding them, so the exact-prefix request never reaches cockpit-ws unnormalized. Deployments whose front end already normalizes or redirects such requests are not exposed through that route. Workaround: Restrict network access to the Cockpit listener (TCP port 9090) to trusted management networks or localhost only, using host firewall rules such as firewalld zones or iptables rules that limit which sources may reach port 9090. If remote access to the Cockpit web console is not required, disable the listener entirely with `systemctl disable --now cockpit.socket`. External connection-rate or concurrency limits in front of TCP port 9090, such as those enforced by a firewall or reverse proxy, further reduce exploitability. Lowering the service's task or file-descriptor ceilings can reduce the blast radius, but does not correct the missing concurrency bound in the cockpit-tls accept path; fixes are being pursued for the affected product streams.

🔗 References (6)