CVE-2026-62182

8.8

KubeEdge · KubeEdge

KubeEdge contains an OS command injection vulnerability in ConfigUpdateJob, allowing an authenticated user to execute arbitrary commands on edge nodes with elevated privileges.

Executive summary

An OS command injection vulnerability in KubeEdge allows authenticated users to execute arbitrary code on target edge nodes, posing a high risk to system integrity and confidentiality.

Vulnerability

This flaw involves improper neutralization of special elements used in an OS command (CWE-78) within the ConfigUpdateJob processing logic. An authenticated user with permissions to create or modify ConfigUpdateJob resources can inject shell metacharacters into the updateFields parameter, leading to command execution with the privileges of the KubeEdge process.

Business impact

Successful exploitation of this vulnerability allows an attacker to gain remote code execution on edge nodes, potentially leading to full system compromise. Given the CVSS score of 8.8, this represents a high-severity risk that could result in unauthorized data access, lateral movement within the edge network, and significant operational disruption.

Remediation

Immediate Action: Upgrade KubeEdge to versions 1.21.2, 1.22.2, or 1.23.1 to apply the necessary security patches.

Proactive Monitoring: Review audit logs for unauthorized creation or modifications of ConfigUpdateJob resources and monitor for suspicious child processes spawned by the KubeEdge service.

Compensating Controls: Implement strict role-based access control (RBAC) to limit which users have the authority to manage ConfigUpdateJob resources until patches can be applied.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This vulnerability presents a significant security risk to KubeEdge deployments due to the potential for remote code execution. Administrators should prioritize upgrading to the patched versions immediately to eliminate the injection vector and protect against potential unauthorized access to edge nodes.

More KubeEdge CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources