GHSA-9vm9-pqxx-x83v: Path Traversal

Published Sep 22, 2026
·
Updated

Description

KubeEdge keadm contains a path traversal vulnerability in the DecompressTarGz archive extraction function.

Archive entry names were joined directly with the extraction destination without sufficient validation. A crafted tar.gz archive containing parent-directory components, Windows-style backslashes, absolute paths, or drive-prefixed paths could cause files to be written outside the intended extraction directory.

The issue is particularly relevant to Windows edge nodes during the keadm join or installation process when keadm extracts downloaded component archives.

Impact

An attacker who can cause an affected keadm process to extract a malicious archive may write or overwrite files outside the intended destination directory with the privileges of the user running keadm.

On Windows edge nodes, this may allow modification of configuration files, executable files, service-related files, or other writable system locations. Depending on the overwritten file and the privileges of the keadm process, successful exploitation could lead to persistent system modification or code execution.

Exploitation requires the attacker to influence the contents of an archive processed by keadm, such as through a compromised, replaced, or otherwise untrusted download source.

Patches

The extraction logic now:

resolves the destination directory to an absolute path; rejects empty archive entry names; normalizes Windows-style path separators before validation; rejects parent-directory traversal paths; rejects absolute and Windows drive-prefixed paths; uses filepath-securejoin to ensure extracted files remain within the destination directory.

Fixes are planned for the following maintained releases:

v1.23.1 v1.22.2 v1.21.2

Workarounds

Until a patched release is available:

only install or join edge nodes using trusted KubeEdge package sources; verify the integrity and origin of downloaded archives before extraction; do not use custom or untrusted component archives with keadm; restrict write permissions and administrative privileges for the account running keadm; avoid performing Windows edge-node installation or join operations when the package source cannot be trusted.

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 Software

3 affected componentsFixes available
go/github.com/kubeedge/kubeedge>=1.23.0<1.23.1
1.23.1
go/github.com/kubeedge/kubeedge>=1.22.0<1.22.2
1.22.2
go/github.com/kubeedge/kubeedge>=1.16.0<1.21.2
1.21.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.23.1
  2. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.22.2
  3. Upgrade

    Upgrade go/github.com/kubeedge/kubeedge to a version that resolves this vulnerability.

    Fixed in 1.21.2
  4. Upgrade

    Upgrade KubeEdge keadm to a version that resolves this vulnerability.

    Fixed in v1.21.2
  5. Upgrade

    Upgrade KubeEdge keadm to a version that resolves this vulnerability.

    Fixed in v1.22.2
  6. Upgrade

    Upgrade KubeEdge keadm to a version that resolves this vulnerability.

    Fixed in v1.23.1
  7. Compensating control

    Only perform Windows edge-node installation or join operations with KubeEdge package sources and component archives whose integrity and origin have been verified; do not use custom or untrusted archives with keadm.

  8. Compensating control

    Restrict write permissions and administrative privileges for the account running keadm.

Event History

Sep 22, 2026
Advisory Published
via GitHub·08:36 PM
Data Sourced
via GitHub·08:36 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are most exposed to this issue?

Windows edge nodes are particularly exposed when keadm performs a join or installation and extracts downloaded component archives. The impact depends on the privileges of the user running keadm and which files that user can overwrite.

2

What must an attacker control to exploit the vulnerability?

An attacker must be able to cause an affected keadm process to extract a crafted tar.gz archive. The archive can use parent-directory components, backslashes, absolute paths, or drive-prefixed paths to target files outside the extraction directory.

3

What can a successful exploit do?

It can write or overwrite files outside the intended extraction destination with the privileges of the keadm process. On Windows, this may affect configuration, executable, service-related, or other writable files, potentially resulting in persistent modification or code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203