# CVE-2026-4802: Cockpit: cockpit: arbitrary command execution via crafted links in system logs ui > Remote attackers can execute arbitrary shell commands on the host by injecting metacharacters into system logs UI links, leading to full system compromise. - **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 11 May 2026 - **Updated:** 15 Jul 2026 - **Also known as:** ALSA-2026:21468, ALSA-2026:21676, ALSA-2026:21700, CLSA-2026-1780323631, DEBIAN-CVE-2026-4802, GHSA-3wjm-5g86-c6p3, RHSA-2026:21390, RHSA-2026:21392, RHSA-2026:21394, RHSA-2026:21395, RHSA-2026:21468, RHSA-2026:21515, RHSA-2026:21516, RHSA-2026:21647, RHSA-2026:21676, RHSA-2026:21700, RLSA-2026:21468, RLSA-2026:21676, RLSA-2026:21700, SUSE-SU-2026:21872-1, UBUNTU-CVE-2026-4802, openSUSE-SU-2026:10819-1, openSUSE-SU-2026:21208-1 ## What is CVE-2026-4802? CVE-2026-4802 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description A flaw was found in Cockpit. This vulnerability allows a remote attacker to achieve arbitrary command execution on the host by exploiting unsanitized user-controlled parameters within crafted links in the system logs user interface (UI). An attacker can inject shell metacharacters and command substitutions into these parameters, leading to the execution of arbitrary shell commands on the affected system. This could result in a complete system compromise. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2026-4802? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cockpit` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-bridge` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-doc` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-packagekit` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-storaged` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-system` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-ws` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit-ws-selinux` | AlmaLinux:10 | All versions | 356.2-1.el10_2 | | `cockpit` | AlmaLinux:8 | All versions | 310.8-1.el8_10 | | `cockpit-bridge` | AlmaLinux:8 | All versions | 310.8-1.el8_10 | | `cockpit-doc` | AlmaLinux:8 | All versions | 310.8-1.el8_10 | | `cockpit-system` | AlmaLinux:8 | All versions | 310.8-1.el8_10 | | `cockpit-ws` | AlmaLinux:8 | All versions | 310.8-1.el8_10 | | `cockpit` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-bridge` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-doc` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-packagekit` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-storaged` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-system` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-ws` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit-ws-selinux` | AlmaLinux:9 | All versions | 356.2-1.el9_8 | | `cockpit` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-bridge` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-doc` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-packagekit` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-storaged` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-system` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-ws` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit-ws-selinux` | Red Hat:enterprise_linux:10.2 | All versions | 0:356.2-1.el10_2 | | `cockpit` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-bridge` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-doc` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-system` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-ws` | Red Hat:enterprise_linux:8::baseos | All versions | 0:310.8-1.el8_10 | | `cockpit-packagekit` | Red Hat:enterprise_linux:9::appstream | All versions | 0:356.2-1.el9_8 | | `cockpit-storaged` | Red Hat:enterprise_linux:9::appstream | All versions | 0:356.2-1.el9_8 | ## How do I fix CVE-2026-4802? Apply the vendor's patch. ## Is CVE-2026-4802 being exploited? There is no known exploitation of CVE-2026-4802 in the wild and no public exploit code. Public exploit code: - Arbitrary command execution on Cockpit (github_poc): https://github.com/hakaioffsec/CVE-2026-4802 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-4802 and fix it if it is affected. What it is: CVE-2026-4802 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-4802 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-4802/ (Markdown: https://insights.sbomify.com/CVE-2026-4802/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4802 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4802 - OSV: https://osv.dev/vulnerability/CVE-2026-4802 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-4802/ Summaries are generated and may contain mistakes; the official description above is the record.