# 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. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`) - **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:** Yes - **Published:** 21 Sep 2026 - **Updated:** 24 Sep 2026 - **Also known as:** GHSA-9vm9-pqxx-x83v, GO-2026-6563 ## 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 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-62369? 7 open source packages ship an affected version, including github.com/kubeedge/kubeedge. | Package | Ecosystem | 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 | | `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. ## Is CVE-2026-62369 being exploited? There is no known exploitation of CVE-2026-62369 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-62369 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-62369 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/kubeedge/kubeedge (Go): affected from 1.16.0; fixed in 1.21.2, 1.22.2, 1.23.1 - github.com/kubeedge/kubeedge (Go): affected from 1.16.0; fixed in 1.21.2 - github.com/kubeedge/kubeedge (Go): affected from 1.16.0; fixed in 1.21.2 - github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2 - github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2 - github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1 - github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-62369/ (Markdown: https://insights.sbomify.com/CVE-2026-62369/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62369 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62369 - OSV: https://osv.dev/vulnerability/CVE-2026-62369 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-62369/ Summaries are generated and may contain mistakes; the official description above is the record.