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

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

Summary

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

Original description

The description as published by the source.

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

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-62182 has been found in github.com/kubeedge/kubeedge.
Attackers can target a specific entry point like updateFields 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-62182" on the vendor's site.

CVE-2026-62182 (github.com/kubeedge/kubeedge) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: updateFields
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 updateFields.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kubeedge/kubeedge. Attack surface: updateFields.

🔥 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