How severe is CVE-2026-62371?

CVE-2026-62371 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-62371?

CVE-2026-62371 affects the following packages: github.com/kubeedge/kubeedge (Go), github.com/kubeedge/kubeedge (Go), github.com/kubeedge/kubeedge (Go). Ecosystems affected: Go.

How do I fix CVE-2026-62371?

Update github.com/kubeedge/kubeedge to 1.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62371 is resolved across your whole dependency graph.

How do I detect CVE-2026-62371 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubeedge/kubeedge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-62371 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-62371 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-62371 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-62371?

CVE-2026-62371 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-62371?

CVE-2026-62371 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-62371 published, and has it been updated?

CVE-2026-62371 was published on September 21, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2026-62371 — kubeedge

HIGHFix: kubeedge/kubeedge@552af45

CVE-2026-62371 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in github.com/kubeedge/kubeedge. A fix is available for github.com/kubeedge/kubeedge — see the affected versions and patch details below.

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

Also known asGHSA-5jpj-293f-rhvjGO-2026-6557

Published

Sep 21, 2026

Updated

Oct 21, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-62371.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-62371 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐹github.com/kubeedge/kubeedge🐹github.com/kubeedge/kubeedge🐹github.com/kubeedge/kubeedge

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kubeedge/kubeedge`	≥ 1.12.0&&< 1.21.2	1.21.2`go get github.com/kubeedge/kubeedge@v1.21.2`
🐹Go	`github.com/kubeedge/kubeedge`	≥ 1.22.0&&< 1.22.2	1.22.2`go get github.com/kubeedge/kubeedge@v1.22.2`
🐹Go	`github.com/kubeedge/kubeedge`	≥ 1.23.0&&< 1.23.1	1.23.1`go get github.com/kubeedge/kubeedge@v1.23.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubeedge/kubeedge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kubeedge/kubeedge to 1.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62371 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

## 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 conf