Skip to main content

KubeEdge keadm EUVDEUVD-2026-84005

| CVE-2026-62369 HIGH
Path Traversal (CWE-22)
2026-09-21 GitHub_M GHSA-9vm9-pqxx-x83v
8.1
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise or substitute component download source
  2. Delivery
    Plant tar.gz with ../ backslash/drive-prefix entries
  3. Exploit
    Operator runs keadm join on Windows edge node
  4. Execution
    DecompressTarGz writes entry outside target dir
  5. Persist
    Overwrite service/executable/config file
  6. Impact
    Persistent modification or code execution

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires all of: (1) the KubeEdge component archive to originate from a compromised, replaced, or untrusted download source rather than the official signed release - the archive itself must be attacker-controlled; (2) a victim operator actively running keadm join or installation (UI:R) on a Windows edge node - the flaw is specifically triggered by Windows-style backslashes, absolute, and drive-prefixed paths in the tar entries; and (3) affected keadm version 1.16.0 through the fixed 1.21.2/1.22.2/1.23.1. Limiting factors: exploitation does NOT occur against official/trusted artifact sources, needs human interaction to launch the install, is scoped to Windows edge nodes, and grants only the privileges the keadm process itself runs with (no confidentiality impact).

Impact

The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H = 8.1 High) presents this as a high-integrity/high-availability flaw, but the description reveals a critical gating precondition that AC:L understates: exploitation requires the archive to arrive from a 'compromised, replaced, or untrusted download source.' Against KubeEdge's normal signed/official artifact sources this does not trigger - it is effectively a supply-chain trust-boundary bug requiring the attacker to first control or substitute the download source and then have a victim run keadm join/install (UI:R). I assess AC:H is more honest than AC:L given that source-compromise prerequisite. There is no EPSS score, no CISA KEV listing, and no public exploit code identified at time of analysis, so this is not evidence of active exploitation - it is a defense-in-depth hardening fix. No SSVC decision framework data was supplied. Net: a legitimately impactful bug (write/overwrite of executables/config/service files → persistence or code execution) but NOT a drop-everything priority - the untrusted-source and user-interaction requirements plus the Windows-edge-node scope make it a targeted/opportunistic rather than mass-exploitable issue. Note also C:N - there is no confidentiality impact, only integrity/availability.

Exploit ScenarioDerived

An attacker compromises or man-in-the-middles the download source (mirror, package host, or CDN) serving the KubeEdge component archive, replacing it with a malicious tar.gz whose entries use ../ sequences, Windows backslashes, or a drive-prefixed absolute path. When an operator runs keadm join or installation on a Windows edge node, DecompressTarGz writes those entries outside the intended directory, overwriting a service binary or config with the keadm process's privileges - yielding persistence or code execution. No public proof-of-concept is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 21, 2026

KubeEdge keadm releases from 1.16.0 before 1.21.2, 1.22.2, and 1.23.1 contain a path traversal in DecompressTarGz that, on Windows edge nodes, can extract archive entries with parent-directory sequences, backslashes, absolute paths, or drive prefixes outside the intended destination. Exploitation requires the operator to run keadm join or installation using an archive obtained from a compromised, replaced, or untrusted download source, making this primarily a supply-chain trust-boundary bug rather than an attack against official artifacts. No public exploit was identified at time of analysis, and vendor fixes are released in 1.21.2, 1.22.2, and 1.23.1.

RemediationAI

Vendor-released patch: 1.21.2, 1.22.2, and 1.23.1; upgrade keadm to the appropriate fixed release for the deployed KubeEdge branch using the vendor advisory at https://github.com/kubeedge/kubeedge/security/advisories/GHSA-9vm9-pqxx-x83v and the release notes at https://github.com/kubeedge/kubeedge/releases/tag/v1.21.2, https://github.com/kubeedge/kubeedge/releases/tag/v1.22.2, and https://github.com/kubeedge/kubeedge/releases/tag/v1.23.1. Until upgrading, obtain KubeEdge archives only from official signed release sources and verify checksums or signatures before running keadm join/install, because the exploit requires an attacker-influenced archive; using internal mirrors or third-party tarballs carries residual risk and should be avoided unless the artifacts are independently validated. Limit the privileges used to run keadm on Windows edge nodes and restrict write access to configuration, executable, and service paths where operationally feasible; these compensating controls can reduce impact if a crafted archive is extracted but may hinder legitimate edge provisioning and upgrade workflows.

Affected VersionsENISA

kubeedge 1.22.0, < 1.22.2
kubeedge 1.16.0, < 1.21.2
kubeedge 1.23.0, < 1.23.1

Affected Packages

go github.com/kubeedge/kubeedge fix: 1.21.2, 1.22.2, 1.23.1
euvd kubeedge_1_16_0 fix: 1.21.2
euvd kubeedge_1_22_0 fix: 1.22.2
euvd kubeedge_1_23_0 fix: 1.23.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

KubeEdge keadm is the command-line lifecycle utility used to bootstrap and join edge nodes; the vulnerable DecompressTarGz function in keadm/cmd/keadm/app/cmd/util/common.go joins tar.gz archive entry names to the extraction destination without sufficient canonicalization or rejection of traversal sequences. The root cause is CWE-22, with Windows-specific parsing complications: backslashes, drive-prefixed paths, and absolute paths can escape the intended directory and cause the keadm process to write or overwrite files with its own privileges. The independent assessment rates this CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H, adjusting the vendor AC:L to AC:H because the attacker must first control, replace, or substitute the download source and then induce an operator to run keadm join or install on a Windows edge node. The C:N reflects no confidentiality impact, while I:H/A:H reflect potential modification of configuration, executable, or service files leading to persistence or code execution. References include advisory GHSA-9vm9-pqxx-x83v, PRs 7028-7030, commits 47767b7f2649afcfa3a856e87d556f7777e0428d, a524a66a1ae1691eb8ff16b6ff9a93fb370d4047, and ee02dea9d08114afc4a8f401b1c2f30e84e1de40, plus CHANGELOG-1.21/1.22/1.23 and release tags v1.21.2, v1.22.2, and v1.23.1. The provided source-code evidence from PR 7028 shows related admission-controller validation hardening (version/image validation and patch operation changes), while the CVE description attributes the path traversal to DecompressTarGz.

Know when Kubeedge gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
vuln.today AI 6.8 MEDIUM

Archive delivered over network (AV:N) but attacker must first compromise/substitute the download source and victim must run keadm (AC:H, UI:R); write/overwrite yields I:H/A:H, no data disclosure (C:N).

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Sep 21, 2026 - 18:02 EUVD
CVE Published
Sep 21, 2026 - 17:10 cve.org
HIGH 8.1

DescriptionCVE.org

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.

Technical POC Analysis

Evidence basis: GitHub Security Advisory GHSA-9vm9-pqxx-x83v and the CVE-2026-62369 description.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

KubeEdge keadm, used for deploying and managing edge nodes, has a high-severity path traversal vulnerability affecting Windows edge nodes. Organizations using keadm versions 1.16.0 through 1.21.1, 1.22.0-1.22.1, or 1.23.0 could be impacted if installation archives are obtained from compromised or untrusted sources, allowing attackers to write files outside intended directories. No public exploit identified at time of analysis, but the supply-chain nature and potential for node compromise warrant leadership attention.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Low
niche CNCF edge orchestration; Windows edge-node install path even narrower
Threat Intel
1
1 source
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-82473 HIGH POC
8.8 Aug 29

Unauthenticated integrity manipulation in KubeEdge CloudCore through 1.23.1 allows any network-reachable attacker to sub

CVE-2022-31073 HIGH POC
7.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31076 MEDIUM POC
5.7 Jun 27

KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to ho

CVE-2026-62371 HIGH
8.8 Sep 21

Shell command injection in KubeEdge's v1alpha2 NodeUpgradeJob upgrade workflow allows an authenticated user who holds RB

CVE-2026-62182 HIGH
8.8 Sep 21

Authenticated command injection in KubeEdge (1.21.0 up to 1.21.2, 1.22.2, and 1.23.1) lets a principal holding Kubernete

CVE-2026-62370 MEDIUM
6.5 Sep 21

Memory exhaustion in KubeEdge CloudHub (versions 1.0.0 through 1.21.1, 1.22.0 through 1.22.1, and 1.23.0) allows an auth

CVE-2022-31080 MEDIUM
6.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31079 MEDIUM
6.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31078 MEDIUM
6.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31075 MEDIUM
6.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31074 MEDIUM
6.5 Jul 11

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at

CVE-2022-31077 MEDIUM
5.7 Jun 27

KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to ho

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy