Is CVE-2026-62371 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62371 being exploited in the wild.

How severe is CVE-2026-62371?

High severity, with a CVSS score of 8.8, published 21 September 2026.

Which products and versions are affected?

github.com/kubeedge/kubeedge (Go) SEMVER:introduced=1.12.0,fixed=1.21.2, SEMVER:introduced=1.12.0,fixed=1.21.2,introduced=1.22.0,fixed=1.22.2,introduced=1.23.0,fixed=1.23.1; KubeEdge before v1.23.1, v1.22.2, v1.21.2.

Is there a fix for CVE-2026-62371?

Yes. github.com/kubeedge/kubeedge (Go): upgrade to 1.21.2, 1.23.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62371 attacked?

It is attacked over the network.

Am I affected by CVE-2026-62371?

Check whether you run github.com/kubeedge/kubeedge (Go) or KubeEdge at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62371: KubeEdge command injection in NodeUpgradeJob via v1alpha2 API

CVE-2026-62371 · Severity: high · CVSS 8.8 · Published 2026-09-21

KubeEdge is a Kubernetes-based edge computing platform that extends cloud native capabilities to edge nodes. An authenticated attacker with permissions to create or update node upgrade jobs could inject shell commands through user-controllable fields, leading to remote code execution on edge nodes with the privileges of the upgrade process, potentially compromising node confidentiality, integrity, and availability.

Technologies: github.com/kubeedge/kubeedge (Go). Vendors: Go, KubeEdge.

Quick answers

Is CVE-2026-62371 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62371 being exploited in the wild.
How severe is CVE-2026-62371?: High severity, with a CVSS score of 8.8, published 21 September 2026.
Which products and versions are affected?: github.com/kubeedge/kubeedge (Go) SEMVER:introduced=1.12.0,fixed=1.21.2, SEMVER:introduced=1.12.0,fixed=1.21.2,introduced=1.22.0,fixed=1.22.2,introduced=1.23.0,fixed=1.23.1; KubeEdge before v1.23.1, v1.22.2, v1.21.2.
Is there a fix for CVE-2026-62371?: Yes. github.com/kubeedge/kubeedge (Go): upgrade to 1.21.2, 1.23.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62371 attacked?: It is attacked over the network.
Am I affected by CVE-2026-62371?: Check whether you run github.com/kubeedge/kubeedge (Go) or KubeEdge at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/kubeedge/kubeedge (Go): upgrade to 1.21.2, 1.23.1 or later
```
go get github.com/kubeedge/kubeedge@v1.23.1
```

Technical details

This is a command injection vulnerability in the NodeUpgradeJob handler where the version and image fields are concatenated into a shell command string without proper escaping or argument separation. An authenticated user can include shell metacharacters (e.g., backticks, pipes, semicolons) in the spec.version or spec.image fields when creating or updating NodeUpgradeJob resources via the v1alpha2 API. When the upgrade job is processed, the injected commands are executed on the targeted edge node with the privileges of the keadm upgrade process. The fix eliminates shell-based command construction by using exec.Command with a structured argument list, ensuring version and image values are passed as literal arguments rather than being interpreted by the shell.

Affected products

KubeEdge KubeEdge before v1.23.1, v1.22.2, v1.21.2

Identifiers

CVE-2026-62371
GHSA-5jpj-293f-rhvj
GO-2026-6557

Timeline

2026-09-22: disclosed
2026-09-22: patched: v1.23.1, v1.22.2, v1.21.2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.