The vulnerability arises in a function that parses viaduct messages and allocates memory solely based on a 32‑bit length field supplied in the message header. Because the length is not bounded before allocation, a maliciously crafted header can cause the CloudHub process to consume excessive memory, terminate, or enter a restart loop, effectively disabling communication between the cloud and edge devices. The flaw does not allow unauthenticated access or arbitrary code execution; it only permits a DoS when the attacker controls a credentialed edge peer that can send such messages.

KubeEdge, the open‑source edge computing platform, is affected in the releases from version 1.0.0 through 1.21.2, as well as the individual releases 1.22.2 and 1.23.1. Those builds trust the payload length field without validating an upper bound.

The CVSS score of 6.5 ranks the issue as moderately severe. No EPSS value is available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires that an attacker be authenticated to an edge peer that can send CloudHub viaduct messages, after which the attacker can repeatedly send oversized headers to exhaust memory and cause the CloudHub process to crash or restart. The impact is limited to denial of service for affected CloudHub instances, and the likelihood of exploitation depends on the attacker’s ability to compromise or control an edge peer.