Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62369 high CVSS 8.1

Path Traversal in github.com/kubeedge/kubeedge (CVE-2026-62369)

Summary

Path traversal in github.com/kubeedge/kubeedge (CVE-2026-62369). Data can be tampered with by attackers. Exploitable via keadm. Mitigation: upgrade to 1.23.1 or later.

Original description

The description as published by the source.

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 va…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-62369 has been found in github.com/kubeedge/kubeedge.
Attackers can target a specific entry point like keadm over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade github.com/kubeedge/kubeedge to 1.23.1 or later.
If unsure, ask your IT team or search "github.com/kubeedge/kubeedge CVE-2026-62369" on the vendor's site.

CVE-2026-62369 (github.com/kubeedge/kubeedge) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: keadm / DecompressTarGz
Patched: 1.23.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/kubeedge/kubeedge. Attackers reach the vulnerable code path via keadm without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kubeedge/kubeedge. Attack surface: keadm / DecompressTarGz.

🔥 Severity

Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.23.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/kubeedge/kubeedge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/kubeedge/kubeedge' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/kubeedge/kubeedge を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/kubeedge/kubeedge to 1.23.1

    ステージング環境で 1.23.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/kubeedge/kubeedge
[{"type":"SEMVER","events":[{"introduced":"1.23.0"},{"fixed":"1.23.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details