Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62371 high CVSS 8.8

OS Command Injection in github.com/kubeedge/kubeedge (CVE-2026-62371)

Summary

OS command injection in github.com/kubeedge/kubeedge (CVE-2026-62371). Successful exploitation can lead to full system takeover. Exploitable via spec.version. Mitigation: upgrade to 1.23.1 or later.

Original description

The description as published by the source.

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 resp…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-62371 has been found in github.com/kubeedge/kubeedge.
Attackers can target a specific entry point like spec.version over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/kubeedge/kubeedge to 1.23.1 or later.
If unsure, ask your IT team or search "github.com/kubeedge/kubeedge CVE-2026-62371" on the vendor's site.

CVE-2026-62371 (github.com/kubeedge/kubeedge) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: spec.version / spec.image / NodeUpgradeJob / keadm
Patched: 1.23.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in github.com/kubeedge/kubeedge. Attackers reach the vulnerable code path via spec.version.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kubeedge/kubeedge. Attack surface: spec.version / spec.image / NodeUpgradeJob / keadm.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.23.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/kubeedge/kubeedge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/kubeedge/kubeedge' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/kubeedge/kubeedge を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/kubeedge/kubeedge to 1.23.1

    ステージング環境で 1.23.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/kubeedge/kubeedge
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.23.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details