CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8). EPSS 15% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-4631 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-4631?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-4631?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-4631 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat Enterprise Linux 10 | 0:344-3.el10_1 |
| Red Hat Enterprise Linux 10 | 0:356.1-1.el10_2 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | 0:334.1-3.el10_0 |
| Red Hat Enterprise Linux 9 | 0:356.1-1.el9_8 |
| Red Hat Enterprise Linux 9 | 0:344-2.el9_7 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | 0:334.2-2.el9_6 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | cockpit | 337-1+deb13u1 | DEBIAN-CVE-2026-4631 |
| Debian | 14 | cockpit | 360-1 | DEBIAN-CVE-2026-4631 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 25.10 and 1 more | cockpit | no fix listed | UBUNTU-CVE-2026-4631 |
| Red Hat | enterprise_linux:9::appstream | cockpit-storaged, cockpit-packagekit | 0:344-2.el9_7 | RHSA-2026:7384 |
| Red Hat | enterprise_linux:9::appstream | cockpit-storaged, cockpit-packagekit | 0:356.1-1.el9_8 | RHBA-2026:21387 |
| Red Hat | enterprise_linux:9::baseos | cockpit, cockpit-ws, cockpit-doc and 5 more | 0:344-2.el9_7 | RHSA-2026:7384 |
| Red Hat | enterprise_linux:9::baseos | cockpit, cockpit-ws, cockpit-doc and 5 more | 0:356.1-1.el9_8 | RHBA-2026:21387 |
| Red Hat | enterprise_linux:10.1 | cockpit, cockpit-ws, cockpit-doc and 7 more | 0:344-3.el10_1 | RHSA-2026:7383 |
| Red Hat | enterprise_linux:10.2 | cockpit, cockpit-ws, cockpit-doc and 7 more | 0:356.1-1.el10_2 | RHBA-2026:21388 |
| Red Hat | enterprise_linux_eus:10.0 | cockpit, cockpit-ws, cockpit-doc and 6 more | 0:334.1-3.el10_0 | RHSA-2026:7381 |
| Red Hat | rhel_eus:9.6::appstream | cockpit-storaged, cockpit-packagekit | 0:334.2-2.el9_6 | RHSA-2026:7382 |
| Red Hat | rhel_eus:9.6::baseos | cockpit, cockpit-ws, cockpit-doc and 4 more | 0:334.2-2.el9_6 | RHSA-2026:7382 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit | 354-160000.3.1 | SUSE-SU-2026:21184-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit | 364-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit-machines | 354-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit-packages | 5-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit-podman | 128-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit-repos | 4.8-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | cockpit-subscriptions | 16.2-160000.1.1 | SUSE-SU-2026:22837-1 |
| SUSE | Linux Micro 6.2 | cockpit | 354-160000.3.1 | SUSE-SU-2026:21106-1 |
| SUSE | Linux Micro 6.2 | cockpit | 364-160000.1.1 | SUSE-SU-2026:22770-1 |
| SUSE | Linux Micro 6.2 | cockpit-machines | 354-160000.1.1 | SUSE-SU-2026:22770-1 |
| SUSE | Linux Micro 6.2 | cockpit-podman | 128-160000.1.1 | SUSE-SU-2026:22770-1 |
| SUSE | Linux Micro 6.2 | cockpit-repos | 4.8-160000.1.1 | SUSE-SU-2026:22770-1 |
| 1 more for SUSE in the JSON and on SUSE's page. | ||||
| openSUSE | Leap 16.0 | cockpit | 354-160000.3.1 | openSUSE-SU-2026:20523-1 |
| openSUSE | Leap 16.0 | cockpit | 364-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Leap 16.0 | cockpit-machines | 354-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Leap 16.0 | cockpit-packages | 5-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Leap 16.0 | cockpit-podman | 128-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Leap 16.0 | cockpit-repos | 4.8-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Leap 16.0 | cockpit-subscriptions | 16.2-160000.1.1 | openSUSE-SU-2026:21399-1 |
| openSUSE | Tumbleweed | cockpit | 360-1.1 | openSUSE-SU-2026:10531-1 |
| AlmaLinux | 9 | cockpit, cockpit-ws, cockpit-doc and 5 more | 344-2.el9_7 | ALSA-2026:7384 |
| AlmaLinux | 10 | cockpit-doc, cockpit-bridge, cockpit-system and 2 more | 344-3.el10_1 | ALSA-2026:7383 |
| Rocky Linux | 9 | cockpit | 0:344-2.el9_7.rocky.0.1 | RLSA-2026:7384 |
| Rocky Linux | 10 | cockpit | 0:344-3.el10_1.rocky.0.1 | RLSA-2026:7383 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.
Red Hat rates this Critical.
Two configuration factors determine whether a Cockpit installation is vulnerable to remote code execution.
First, the hostname injection attack (injecting SSH options like -oProxyCommand via the URL path) is blocked by OpenSSH 9.6 and later, which validates hostnames and rejects shell metacharacters before establishing a connection. Systems running Cockpit 327 or later with an OpenSSH version older than 9.6 are vulnerable to unauthenticated remote code execution in the default configuration. Systems with OpenSSH 9.6 or later are not vulnerable to this attack path.
Second, the username injection attack (injecting shell commands via the SSH username) requires that the system's SSH configuration uses the %r (remote username) token within a Match exec directive. This is not part of any default OpenSSH configuration. Systems that do not use %r in a Match exec directive are not vulnerable to this attack path, regardless of OpenSSH version.
Both attack paths require network access to the Cockpit web service (port 9090 by default) and that remote host login is enabled, which is the default Cockpit configuration.
This security issue was introduced in Cockpit version 327. Due to that, the cockpit packages as shipped with Red Hat Enterprise Linux 8, and Red Hat Enterprise Linux 9 before release 9.6, were not affected by this flaw.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | cockpit-0:344-3.el10_1 | Fixed 2026-04-10 | RHSA-2026:7383 |
| Red Hat Enterprise Linux 10 | cockpit-0:356.1-1.el10_2 | Fixed 2026-05-27 | RHBA-2026:21388 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | cockpit-0:334.1-3.el10_0 | Fixed 2026-04-10 | RHSA-2026:7381 |
| Red Hat Enterprise Linux 9 | cockpit-0:356.1-1.el9_8 | Fixed 2026-05-27 | RHBA-2026:21387 |
| Red Hat Enterprise Linux 9 | cockpit-0:344-2.el9_7 | Fixed 2026-04-10 | RHSA-2026:7384 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | cockpit-0:334.2-2.el9_6 | Fixed 2026-04-10 | RHSA-2026:7382 |
| Red Hat Enterprise Linux 7 | cockpit | Not affected | |
| Red Hat Enterprise Linux 8 | cockpit | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-4631.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.