# CVE-2026-62370: KubeEdge: Unbounded allocation in viaduct packer enables authenticated remote DoS against CloudHub

> An authenticated attacker can cause CloudHub memory exhaustion and service disruption by sending crafted viaduct headers with excessive payload lengths.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-gfw4-49f9-cp25, GO-2026-6569

## What is CVE-2026-62370?

CVE-2026-62370 is a medium-severity denial of service vulnerability in kubeedge, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.0.0 until 1.21.2, 1.22.2, and 1.23.1, Reader.Read in pkg/viaduct/pkg/packer trusts the 32-bit PackageHeader.PayloadLen received through the CloudHub viaduct message-processing path and allocates that amount of memory before validating an upper bound. An authenticated malicious or compromised edge peer can repeatedly send crafted headers with excessive declared lengths, causing memory exhaustion, CloudHub process termination or restart loops, and temporary disruption of cloud-edge communication. This issue does not provide unauthenticated access or direct code execution. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2026-62370?

7 open source packages ship an affected version, including github.com/kubeedge/kubeedge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubeedge/kubeedge` | Go | From 1.0.0 | 1.21.2, 1.22.2, 1.23.1 |
| `github.com/kubeedge/kubeedge` | Go | From 1.0.0 | 1.21.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.0.0 | 1.21.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.22.0 | 1.22.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.22.0 | 1.22.2 |
| `github.com/kubeedge/kubeedge` | Go | From 1.23.0 | 1.23.1 |
| `github.com/kubeedge/kubeedge` | Go | From 1.23.0 | 1.23.1 |

## How do I fix CVE-2026-62370?

Upgrade github.com/kubeedge/kubeedge to a fixed version for your release line: 1.21.2, 1.22.2 or 1.23.1.

## Is CVE-2026-62370 being exploited?

There is no known exploitation of CVE-2026-62370 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62370 and fix it if it is affected.

What it is: CVE-2026-62370 is a medium-severity denial of service vulnerability in kubeedge, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62370 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubeedge/kubeedge (Go): affected from 1.0.0; fixed in 1.21.2, 1.22.2, 1.23.1
- github.com/kubeedge/kubeedge (Go): affected from 1.0.0; fixed in 1.21.2
- github.com/kubeedge/kubeedge (Go): affected from 1.0.0; fixed in 1.21.2
- github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2
- github.com/kubeedge/kubeedge (Go): affected from 1.22.0; fixed in 1.22.2
- github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1
- github.com/kubeedge/kubeedge (Go): affected from 1.23.0; fixed in 1.23.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62370/ (Markdown: https://insights.sbomify.com/CVE-2026-62370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62370
- OSV: https://osv.dev/vulnerability/CVE-2026-62370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62370/
Summaries are generated and may contain mistakes; the official description above is the record.