HighGHSA-5jpj-293f-rhvjCVE-2026-62371GO-2026-6557

KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API

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.12.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

Impact

The KubeEdge NodeUpgradeJob handler constructed the keadm upgrade edge command by concatenating the user-controlled spec.version and spec.image fields into a shell command.

An authenticated user with permission to create or update NodeUpgradeJob resources through the v1alpha2 API could include shell metacharacters in either field. When the upgrade job was processed, the injected command could be executed on the targeted edge node with the privileges available to the upgrade process.

Successful exploitation could result in arbitrary command execution and compromise the confidentiality, integrity, and availability of the affected edge node.

Patches

The fix removes shell-based command construction and invokes keadm using a structured argument list through exec.Command.

The version and image values are passed as separate literal arguments and are no longer interpreted by a command shell.

The fixed versions:

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

Workarounds

Until a patched version is available:

  • restrict permission to create or update NodeUpgradeJob resources to trusted administrators;
  • do not allow untrusted users or tenants to control the spec.version or spec.image fields;
  • avoid using NodeUpgradeJob-based edge upgrades in environments where these fields may be influenced by untrusted users.

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-5jpj-293f-rhvj 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-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
  • LowCVE-2026-62182KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodes in github.com/kubeedge/kubeedge · 1 Oct 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
  • HighCVE-2026-62182KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodes · 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.