CVE-2026-62369 json
KubeEdge: keadm DecompressTarGz path traversal enables arbitrary file write on Windows during edge node join
published 2026-09-21 49 d ago modified 2026-10-01 38 d ago also EUVD-2026-84005 , GHSA-9vm9-pqxx-x83v , GO-2026-6563
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/kubeedge/kubeedge 1.21.2, 1.22.2, 1.23.1
- linuxfoundation kubeedge 1.21.2, 1.22.2, 1.23.1
- github.com/kubeedge/kubeedge@47767b7 commit
- github.com/kubeedge/kubeedge@a524a66 commit
- github.com/kubeedge/kubeedge@ee02dea commit
- github.com/kubeedge/kubeedge#7028 pull request
- github.com/kubeedge/kubeedge#7029 pull request
- github.com/kubeedge/kubeedge#7030 pull request
- github.com/kubeedge/kubeedge/releases/tag/v1.21.2 release
- github.com/kubeedge/kubeedge/releases/tag/v1.22.2 release
- github.com/kubeedge/kubeedge/releases/tag/v1.23.1 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kubeedge/kubeedge | >=1.16.0, <1.21.2 >=1.22.0, <1.22.2 >=1.23.0, <1.23.1 |
1.21.2 1.22.2 1.23.1 |
Affected products
- kubeedge kubeedge
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/kubeedge/kubeedge/pull/7028
web, patch
-
github.com
/kubeedge/kubeedge/pull/7029
web, patch
-
github.com
/kubeedge/kubeedge/pull/7030
web, patch
-
github.com
/kubeedge/kubeedge/commit/47767b7f2649afcfa3a856e87d556f7777e0428d
web, patch
-
github.com
/kubeedge/kubeedge/commit/a524a66a1ae1691eb8ff16b6ff9a93fb370d4047
web, patch
-
github.com
/kubeedge/kubeedge/commit/ee02dea9d08114afc4a8f401b1c2f30e84e1de40
web, patch
-
github.com
/kubeedge/kubeedge/security/advisories/GHSA-9vm9-pqxx-x83v
web, advisory
-
github.com
/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md
web
-
github.com
/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.22.md
web
-
github.com
/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.23.md
web
-
github.com
/kubeedge/kubeedge/releases/tag/v1.21.2
web
-
github.com
/kubeedge/kubeedge/releases/tag/v1.22.2
web
-
github.com
/kubeedge/kubeedge/releases/tag/v1.23.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-62369
advisory
-
github.com
/kubeedge/kubeedge
package
Sources
- CVE List CVE-2026-62369
- GitHub Advisory GHSA-9vm9-pqxx-x83v
- NVD CVE-2026-62369
- OSV GO-2026-6563
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.