GHSA-m3c6-2p7h-cfr3: OS Command Injection

Published Sep 22, 2026
·
Updated

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 Software

3 affected componentsFixes available
go/github.com/kubeedge/kubeedge>=1.23.0<1.23.1
1.23.1
go/github.com/kubeedge/kubeedge>=1.22.0<1.22.2
1.22.2
go/github.com/kubeedge/kubeedge>=1.21.0<1.21.2
1.21.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.23.1
  2. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.22.2
  3. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.21.2
  4. Upgrade

    Upgrade KubeEdge to a version that resolves this vulnerability.

    Fixed in v1.21.2
  5. Upgrade

    Upgrade KubeEdge to a version that resolves this vulnerability.

    Fixed in v1.22.2
  6. Upgrade

    Upgrade KubeEdge to a version that resolves this vulnerability.

    Fixed in v1.23.1
  7. Compensating control

    Allow only trusted administrators to submit ConfigUpdateJob resources.

  8. Compensating control

    Avoid using ConfigUpdateJob in environments where its input cannot be fully trusted.

  9. Compensating control

    Restrict RBAC permissions for creating or modifying ConfigUpdateJob resources.

  10. Compensating control

    Monitor ConfigUpdateJob resources and edge-node process activity for unexpected commands or changes.

Event History

Sep 22, 2026
Advisory Published
via GitHub·08:36 PM
Data Sourced
via GitHub·08:36 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which systems are exposed to command execution?

Exposure is limited to enrolled edge nodes that can be targeted by ConfigUpdateJob resources. Commands execute with the privileges of the KubeEdge process that handles the job on the edge node.

2

What access must an attacker have?

The attacker must be authenticated and have sufficient permission to create or modify ConfigUpdateJob resources. They must also be able to target an enrolled edge node.

3

Which releases include the planned fix?

Fixes are planned for maintained releases v1.23.1, v1.22.2, and v1.21.2. The fix passes the complete --set value as one structured literal argument rather than constructing a shell command.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203