CVE-2026-62370 is a medium-severity (CVSS 6.5) CWE-789 vulnerability in github.com/kubeedge/kubeedge. A fix is available for github.com/kubeedge/kubeedge — see the affected versions and patch details below.
KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-62370.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-62370 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/kubeedge/kubeedge🐹github.com/kubeedge/kubeedge🐹github.com/kubeedge/kubeedgeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kubeedge/kubeedge | ≥ 1.0.0&&< 1.21.2 | 1.21.2go get github.com/kubeedge/kubeedge@v1.21.2 |
| 🐹Go | github.com/kubeedge/kubeedge | ≥ 1.22.0&&< 1.22.2 | 1.22.2go get github.com/kubeedge/kubeedge@v1.22.2 |
| 🐹Go | github.com/kubeedge/kubeedge | ≥ 1.23.0&&< 1.23.1 | 1.23.1go get github.com/kubeedge/kubeedge@v1.23.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubeedge/kubeedge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kubeedge/kubeedge to 1.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62370 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2026-62370 in your dependencies?
Find it across Go, including transitive dependencies.