# CVE-2026-62371: KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API

> Authenticated users can inject shell commands into NodeUpgradeJob fields, leading to remote code execution on edge nodes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-5jpj-293f-rhvj, GO-2026-6557

## What is CVE-2026-62371?

CVE-2026-62371 is a high-severity command injection vulnerability in kubeedge, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.12.0 until 1.21.2, 1.22.2, and 1.23.1, the v1alpha2 NodeUpgradeJob handler in edge/pkg/taskmanager/actions/nodeupgradejob.go concatenates authenticated user-controlled spec.version and spec.image values into the keadm upgrade edge shell command. A user with permission to create or update NodeUpgradeJob resources can supply shell metacharacters in either field, causing arbitrary commands to execute on targeted edge nodes with the privileges of the upgrade process and compromising node confidentiality, integrity, and availability. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-62371?

7 open source packages ship an affected version, including github.com/kubeedge/kubeedge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubeedge/kubeedge` | Go | From 1.12.0 | 1.21.2, 1.22.2, 1.23.1 |
| `github.com/kubeedge/kubeedge` | Go | From 1.12.0 | 1.21.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.12.0 | 1.21.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.22.0 | 1.22.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.22.0 | 1.22.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.23.0 | 1.23.1 |
| `github.com/kubeedge/kubeedge` | Go | From 1.23.0 | 1.23.1 |

## How do I fix CVE-2026-62371?

Upgrade github.com/kubeedge/kubeedge to a fixed version for your release line: 1.21.2, 1.22.2 or 1.23.1.

## Is CVE-2026-62371 being exploited?

There is no known exploitation of CVE-2026-62371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62371 and fix it if it is affected.

What it is: CVE-2026-62371 is a high-severity command injection vulnerability in kubeedge, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62371 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubeedge/kubeedge (Go): affected from 1.12.0; fixed in 1.21.2, 1.22.2, 1.23.1
- github.com/kubeedge/kubeedge (Go): affected from 1.12.0; fixed in 1.21.2
- github.com/kubeedge/kubeedge (Go): affected from 1.12.0; fixed in 1.21.2
- github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2
- github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2
- github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1
- github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1

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-62371/ (Markdown: https://insights.sbomify.com/CVE-2026-62371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62371
- OSV: https://osv.dev/vulnerability/CVE-2026-62371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62371/
Summaries are generated and may contain mistakes; the official description above is the record.