Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62370 medium CVSS 6.5

Vulnerability in github.com/kubeedge/kubeedge (CVE-2026-62370)

Summary

Vulnerability in github.com/kubeedge/kubeedge (CVE-2026-62370). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.23.1 or later.

Original description

The description as published by the source.

Summary

KubeEdge CloudHub uses the viaduct packer to decode messages received from connected peers. The packer reads a 32-bit payload length from the message header and previously allocated a buffer of that size without enforcing an upper bound.

An authenticated peer that can establish a viaduct connection to CloudHub can send a crafted message header containing an excessively large payload length. This may cause CloudHub to allocate a large amount of memory and can result in memory exhaustion, process termination, or denial of service.

Impact

A successfully authenticated malicious or compromised edge node may repeatedly send crafted viaduct message headers to increase CloudHub memory consumption.

Depending on available memory and deployment limits, exploitation may cause:

  • Increased CloudHub memory usage
  • Out-of-memory termination
  • CloudHub restart loops
  • Temporary disruption of cloud-edge communication

Authentication to the viaduct endpoint is required. This issue does not provide unauthenticated access or direct code execution.

Root cause

The viaduct packer trusted the payload length encoded in the message header and allocated the payload buffer before validating whether the declared length was within an acceptable range.

Fix

The fix introduces a maximum viaduct payload size of 32 MiB.

The updated implementation:

  • Rejects oversized payload lengths in the reader before memory allocation
  • Enforces the same maximum size in the writer
  • Adds regr…

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-62370 has been found in github.com/kubeedge/kubeedge.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/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-62370" on the vendor's site.

CVE-2026-62370 (github.com/kubeedge/kubeedge) — CWE-789 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
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

A vulnerability (CWE-789) exists in github.com/kubeedge/kubeedge.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kubeedge/kubeedge.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 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":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.23.1"}]}]

References

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