Is CVE-2026-62182 exploited in the wild?

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

How severe is CVE-2026-62182?

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.21.0,fixed=1.21.2, SEMVER:introduced=1.21.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-62182?

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-62182 attacked?

It is attacked over the network.

Am I affected by CVE-2026-62182?

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-62182: KubeEdge ConfigUpdateJob command injection in updateFields

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

KubeEdge is an edge computing platform that extends Kubernetes to edge devices. The ConfigUpdateJob feature, which manages configuration updates on edge nodes, is vulnerable to command injection when processing user-supplied configuration field values. An authenticated attacker with permission to create or modify configuration jobs can inject shell commands that execute with KubeEdge process privileges on targeted edge nodes, potentially compromising system integrity and availability.

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

Quick answers

Is CVE-2026-62182 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62182 being exploited in the wild.
How severe is CVE-2026-62182?: 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.21.0,fixed=1.21.2, SEMVER:introduced=1.21.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-62182?: 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-62182 attacked?: It is attacked over the network.
Am I affected by CVE-2026-62182?: 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

The vulnerability is a command injection flaw in the ConfigUpdateJob processor that concatenates user-controlled `updateFields` values directly into a shell command string without proper sanitization or escaping. The vulnerable component executes the resulting command via a system shell, allowing attackers to inject shell metacharacters and execute arbitrary commands. The attack requires authentication and RBAC permissions to create or modify ConfigUpdateJob resources, and targets enrolled edge nodes. The fix replaces shell-based command construction with structured argument passing, preventing metacharacter interpretation. Patches are available or planned for v1.23.1, v1.22.2, and v1.21.2.

Affected products

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

Identifiers

CVE-2026-62182
GHSA-m3c6-2p7h-cfr3
GO-2026-6573

Timeline

2026-09-22: disclosed
2026-09-22: patched: Fixes planned for 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.