CVE-2026-62369 KubeEdge: keadm DecompressTarGz path traversal enables arbitrary file write on Windows during edge node join
Attackers can write arbitrary files on Windows edge nodes via path traversal in keadm, enabling persistent system modification or code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-62369?
CVE-2026-62369 is a high-severity path traversal vulnerability in kubeedge, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.16.0 until 1.21.2, 1.22.2, and 1.23.1, the DecompressTarGz function in keadm/cmd/keadm/app/cmd/util/common.go joins archive entry names to the extraction destination without sufficient validation. During keadm join or installation on Windows edge nodes, an archive influenced through a compromised, replaced, or untrusted download source can contain parent-directory components, Windows-style backslashes, absolute paths, or drive-prefixed paths that escape the intended directory. The affected keadm process can consequently write or overwrite files with its own privileges, potentially modifying configuration, executable, or service files and enabling persistent system modification or code execution. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.
Weakness: CWE-22
Which versions are affected by CVE-2026-62369?
7 open source packages ship an affected version, including github.com/kubeedge/kubeedge.
| Package | Affected | Fixed in |
|---|---|---|
github.com/kubeedge/kubeedge Go | From 1.16.0 | 1.21.2, 1.22.2, 1.23.1 |
github.com/kubeedge/kubeedge Go | From 1.16.0 | 1.21.2 |
github.com/kubeedge/kubeedge Go | From 1.16.0 | 1.21.2 |
github.com/kubeedge/kubeedge Go | From 1.22.0 | 1.22.2 |
github.com/kubeedge/kubeedge Go | From 1.22.0 | 1.22.2 |
github.com/kubeedge/kubeedge Go | From 1.23.0 | 1.23.1 |
1 more packages
github.com/kubeedge/kubeedge Go | From 1.23.0 | 1.23.1 |
How do I fix CVE-2026-62369?
Upgrade github.com/kubeedge/kubeedge to a fixed version for your release line: 1.21.2, 1.22.2 or 1.23.1.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-62369 being exploited?
There is no known exploitation of CVE-2026-62369 in the wild and no public exploit code.
Sources
Also known as GHSA-9vm9-pqxx-x83v, GO-2026-6563.