github.com/kubeedge/kubeedge
Affected
- introduced
1.21.0, fixed1.21.2(semver)
Fixed versions
1.21.2
Fix
- Fixed version
1.21.2go get github.com/kubeedge/[email protected]
Advisory
Also known as: CVE-2026-62182, GO-2026-6573
KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodes
Description
KubeEdge ConfigUpdateJob processing was vulnerable to command injection on edge nodes.
The updateFields values from a ConfigUpdateJob were concatenated into a command string and executed through a system shell. An authenticated user with sufficient permissions to create or update ConfigUpdateJob resources could include shell metacharacters in the supplied configuration fields and cause unintended commands to be executed on targeted edge nodes.
Impact
Successful exploitation could allow an authenticated attacker to execute arbitrary commands on affected edge nodes with the privileges of the KubeEdge process handling the ConfigUpdateJob.
The attacker must already have permission to create or modify ConfigUpdateJob resources and target an enrolled edge node.
Patches
The fix removes shell-based command construction and invokes keadm config-update using structured command arguments.
The complete --set value is passed as a single literal argument, preventing shell metacharacters from being interpreted as commands.
Fixes are planned for the following maintained releases:
Workarounds
Until a patched release is available:
Credits
KubeEdge thanks Sang-Hoon Choi (KoreaSecurity, Sejong University)
for responsibly reporting this issue and for coordinating with the KubeEdge
maintainers through the security disclosure process.
High Basis: The source's own band: HIGH
1.21.0, fixed 1.21.2 (semver)1.21.2
1.21.2go get github.com/kubeedge/[email protected]1.22.0, fixed 1.22.2 (semver)1.22.2
1.22.2go get github.com/kubeedge/[email protected]1.23.0, fixed 1.23.1 (semver)1.23.1
1.23.1go get github.com/kubeedge/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0