GHSA-5JPJ-293F-RHVJ
Vulnerability from github – Published: 2026-09-22 20:37 – Updated: 2026-09-22 20:37Impact
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
NodeUpgradeJobresources to trusted administrators; - do not allow untrusted users or tenants to control the
spec.versionorspec.imagefields; - 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 responsibly reporting this issue and for coordinating with the KubeEdge maintainers through the security disclosure process.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/kubeedge/kubeedge"
},
"ranges": [
{
"events": [
{
"introduced": "1.12.0"
},
{
"fixed": "1.21.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/kubeedge/kubeedge"
},
"ranges": [
{
"events": [
{
"introduced": "1.22.0"
},
{
"fixed": "1.22.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/kubeedge/kubeedge"
},
"ranges": [
{
"events": [
{
"introduced": "1.23.0"
},
{
"fixed": "1.23.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-62371"
],
"database_specific": {
"cwe_ids": [
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-22T20:37:04Z",
"nvd_published_at": "2026-09-21T17:17:37Z",
"severity": "HIGH"
},
"details": "## Impact\n\nThe KubeEdge NodeUpgradeJob handler constructed the `keadm upgrade edge` command by concatenating the user-controlled `spec.version` and `spec.image` fields into a shell command.\n\nAn 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.\n\nSuccessful exploitation could result in arbitrary command execution and compromise the confidentiality, integrity, and availability of the affected edge node.\n\n## Patches\n\nThe fix removes shell-based command construction and invokes `keadm` using a structured argument list through `exec.Command`.\n\nThe version and image values are passed as separate literal arguments and are no longer interpreted by a command shell.\n\nThe fixed versions:\n\n* KubeEdge v1.23.1\n* KubeEdge v1.22.2\n* KubeEdge v1.21.2\n\n## Workarounds\n\nUntil a patched version is available:\n\n* restrict permission to create or update `NodeUpgradeJob` resources to trusted administrators;\n* do not allow untrusted users or tenants to control the `spec.version` or `spec.image` fields;\n* avoid using NodeUpgradeJob-based edge upgrades in environments where these fields may be influenced by untrusted users.\n\n## Credits\n\nKubeEdge thanks Sang-Hoon Choi ([KoreaSecurity](https://github.com/KoreaSecurity), Sejong University)\nfor responsibly reporting this issue and for coordinating with the KubeEdge\nmaintainers through the security disclosure process.",
"id": "GHSA-5jpj-293f-rhvj",
"modified": "2026-09-22T20:37:04Z",
"published": "2026-09-22T20:37:04Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/security/advisories/GHSA-5jpj-293f-rhvj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-62371"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/pull/7028"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/pull/7029"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/pull/7030"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/commit/552af457a4c7ce80ea1678ab5889f475b36ea103"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/commit/657b745bebcdd7a221eb34c0aac13231ef12c37f"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/commit/b72db7f8a0f7be23261b4349eab33024b2007df0"
},
{
"type": "PACKAGE",
"url": "https://github.com/kubeedge/kubeedge"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.22.md"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.23.md"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/releases/tag/v1.21.2"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/releases/tag/v1.22.2"
},
{
"type": "WEB",
"url": "https://github.com/kubeedge/kubeedge/releases/tag/v1.23.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.