HighGHSA-m3c6-2p7h-cfr3CVE-2026-62182GO-2026-6573

KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodes

Published 22 Sept 2026 · Updated 1 Oct 2026

Is your project on an affected github.com/kubeedge/kubeedge?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.21.0 <1.21.2
Fixed in
1.21.2
Update to the fixed version for your release line, for example:go get github.com/kubeedge/kubeedge@v1.21.2
Affected
>=1.22.0 <1.22.2
Fixed in
1.22.2
Update to the fixed version for your release line, for example:go get github.com/kubeedge/kubeedge@v1.22.2
Affected
>=1.23.0 <1.23.1
Fixed in
1.23.1
Update to the fixed version for your release line, for example:go get github.com/kubeedge/kubeedge@v1.23.1

Details

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:

  • v1.23.1
  • v1.22.2
  • v1.21.2

Workarounds

Until a patched release is available:

  • restrict RBAC permissions for creating or modifying ConfigUpdateJob resources;
  • allow only trusted administrators to submit configuration update jobs;
  • avoid using ConfigUpdateJob in environments where its input cannot be fully trusted;
  • monitor ConfigUpdateJob resources and edge-node process activity for unexpected commands or changes.

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.

Is GHSA-m3c6-2p7h-cfr3 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/kubeedge/kubeedge, and gives you the command that fixes it.

More advisories for github.com/kubeedge/kubeedge

  • LowCVE-2026-62371KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API in github.com/kubeedge/kubeedge · 1 Oct 2026
  • LowCVE-2026-62369KubeEdge: keadm DecompressTarGz path traversal enables arbitrary file write on Windows during edge node join in github.com/kubeedge/kubeedge · 1 Oct 2026
  • LowCVE-2026-62370KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub in github.com/kubeedge/kubeedge · 1 Oct 2026
  • HighCVE-2026-62371KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API · 22 Sept 2026
  • MediumCVE-2026-62370KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub · 22 Sept 2026
  • HighCVE-2026-62369KubeEdge: keadm DecompressTarGz path traversal enables arbitrary file write on Windows during edge node join · 22 Sept 2026
All 23 advisories for github.com/kubeedge/kubeedge

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.