CVE-2026-62370: KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub
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.
Published Sep 22, 2026
Affected packages
github.com/kubeedge/kubeedge
- Ecosystem
- Go
- Affected
- >= 1.0.0, < 1.21.2
- Fixed in
- 1.21.2
- Check
go list -m github.com/kubeedge/kubeedge
github.com/kubeedge/kubeedge
- Ecosystem
- Go
- Affected
- >= 1.22.0, < 1.22.2
- Fixed in
- 1.22.2
- Check
go list -m github.com/kubeedge/kubeedge
github.com/kubeedge/kubeedge
- Ecosystem
- Go
- Affected
- >= 1.23.0, < 1.23.1
- Fixed in
- 1.23.1
- Check
go list -m github.com/kubeedge/kubeedge
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 regression tests covering oversized and valid payloads
Fixes have been prepared for the following patch releases:
- KubeEdge v1.23.1
- KubeEdge v1.22.2
- KubeEdge v1.21.2
These versions should not be listed as released until the coordinated release process is complete.
Workarounds
Before patched versions are available, operators should:
- Restrict access to the CloudHub endpoint to trusted edge nodes and networks
- Protect and rotate edge-node credentials
- Revoke credentials belonging to decommissioned or potentially compromised nodes
- Apply memory limits and restart policies to the CloudHub workload
- Monitor CloudHub memory consumption and unexpected connection activity
Affected component
pkg/viaduct/pkg/packer- CloudHub viaduct message-processing path
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.
Credited to DoisLONG, kevin-wangzefeng.
References
- https://github.com/kubeedge/kubeedge/security/advisories/GHSA-gfw4-49f9-cp25
- https://nvd.nist.gov/vuln/detail/CVE-2026-62370
- https://github.com/kubeedge/kubeedge/pull/7028
- https://github.com/kubeedge/kubeedge/pull/7029
- https://github.com/kubeedge/kubeedge/pull/7030
- https://github.com/kubeedge/kubeedge/commit/0fe1ea18e5d7fde29633286ddf1c7e71cb39606f
- https://github.com/kubeedge/kubeedge/commit/725a73ca35a65d91aa6338e52b8faaab6058f528
- https://github.com/kubeedge/kubeedge/commit/cc79621943fff9d3f62638d9403ef0cfeda3d0e7
- https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md
- https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.22.md
- https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.23.md
- https://github.com/kubeedge/kubeedge/releases/tag/v1.21.2
- https://github.com/kubeedge/kubeedge/releases/tag/v1.22.2
- https://github.com/kubeedge/kubeedge/releases/tag/v1.23.1
- https://github.com/advisories/GHSA-gfw4-49f9-cp25
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-62182
KubeEdge: ConfigUpdateJob updateFields enables remote shell injection and code execution on edge nodes
high8.8Sep 22, 2026CVE-2026-62369
KubeEdge: keadm DecompressTarGz path traversal enables arbitrary file write on Windows during edge node join
high8.1Sep 22, 2026CVE-2026-62371
KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API
high8.8Sep 22, 2026
