Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodesGHSA-m3c6-2p7h-cfr3

HIGHFix: kubeedge/kubeedge#7028

GHSA-m3c6-2p7h-cfr3 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.

Also known asCVE-2026-62182GO-2026-6573
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 23, 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 GHSA-m3c6-2p7h-cfr3.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.5%0.5%Oct 26Oct 26

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

How urgent is this, really

GHSA-m3c6-2p7h-cfr3 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

Description

KubeEdge ConfigUpdateJob processing was vulnerable to command injection on edge nodes.

The updateFields values from a ConfigUpdateJob were concatenated into a command string and executed through a system shell. An authenticated user with sufficient permissions to create or update ConfigUpdateJob resources could include shell metacharacters in the supplied configuration fields and cause unintended commands to be executed on targeted edge nodes.

Impact

Successful exploitation could allow an authenticated attacker to execute arbitrary commands on affected edge nodes with the privileges of the KubeEdge process handling the ConfigUpdateJob.

The attacker must already have permission to create or modify ConfigUpdateJob resources and target an enrolled edge node.

Patches

The fix removes shell-based command construction and invokes keadm config-update using structured command arguments.

The complete --set value is passed as a single literal argument, preventing shell metacharacters from being interpreted as commands.

Fixes are planned for the following maintained releases:

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

Workarounds

Until a patched release is available:

  • restrict RBAC permissions for creating or modifying ConfigUpdateJob resources;
  • allow only trusted administrators to submit configuration update jobs;
  • avoid using ConfigUpdateJob in environments where its input cannot be fully trusted;
  • monitor ConfigUpdateJob resources and edge-node process activity for unexpected commands or changes.

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
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubeedge/kubeedge≥ 1.21.0&&< 1.21.21.21.2go get github.com/kubeedge/kubeedge@v1.21.2
🐹Gogithub.com/kubeedge/kubeedge≥ 1.22.0&&< 1.22.21.22.2go get github.com/kubeedge/kubeedge@v1.22.2
🐹Gogithub.com/kubeedge/kubeedge≥ 1.23.0&&< 1.23.11.23.1go get github.com/kubeedge/kubeedge@v1.23.1

Detection & mitigation playbook

Open-source dependency

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

  2. 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 GHSA-m3c6-2p7h-cfr3 is resolved across your whole dependency graph.

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

## Description KubeEdge ConfigUpdateJob processing was vulnerable to command injection on edge nodes. The `updateFields` values from a ConfigUpdateJob were concatenated into a command string and executed through a system shell. An authenticated user with sufficient permissions to create or update ConfigUpdateJob resources could include shell metacharacters in the supplied configuration fields and cause unintended commands to be executed on targeted edge nodes. ## Impact Successful exploitation could allow an authenticated attacker to execute arbitrary commands on affected edge nodes with t
O3 Security · Impact-Aware SCA

Is GHSA-m3c6-2p7h-cfr3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
KubeEdge: ConfigUpdateJob updateFields enables remote…