https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 14:58:21 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-62370 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-62370 https://vulnerability.circl.lu/vuln/ghsa-gfw4-49f9-cp25 <p><strong>Affected:</strong> Go: github.com/kubeedge/kubeedge</p> <p>## Summary</p> <p>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.</p> <p>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.</p> <p>## Impact</p> <p>A successfully authenticated malicious or compromised edge node may repeatedly send crafted viaduct message headers to increase CloudHub memory consumption.</p> <p>Depending on available memory and deployment limits, exploitation may cause:</p> <p>* Increased CloudHub memory usage * Out-of-memory termination * CloudHub restart loops * Temporary disruption of cloud-edge communication</p> <p>Authentication to the viaduct endpoint is required. This issue does not provide unauthenticated access or direct code execution.</p> <p>## Root cause</p> <p>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.</p> <p>## Fix</p> <p>The fix introduces a maximum viaduct payload size of 32 MiB.</p> <p>The updated implementation:</p> <p>* Rejects oversized payload lengths in the reader before memory allocation * Enforces the same maximum size in the writer * Adds reg…</p> <p><strong>Affected:</strong> Go: github.com/kubeedge/kubeedge</p> <p>## Summary</p> <p>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.</p> <p>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.</p> <p>## Impact</p> <p>A successfully authenticated malicious or compromised edge node may repeatedly send crafted viaduct message headers to increase CloudHub memory consumption.</p> <p>Depending on available memory and deployment limits, exploitation may cause:</p> <p>* Increased CloudHub memory usage * Out-of-memory termination * CloudHub restart loops * Temporary disruption of cloud-edge communication</p> <p>Authentication to the viaduct endpoint is required. This issue does not provide unauthenticated access or direct code execution.</p> <p>## Root cause</p> <p>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.</p> <p>## Fix</p> <p>The fix introduces a maximum viaduct payload size of 32 MiB.</p> <p>The updated implementation:</p> <p>* Rejects oversized payload lengths in the reader before memory allocation * Enforces the same maximum size in the writer * Adds reg…</p> https://vulnerability.circl.lu/vuln/ghsa-gfw4-49f9-cp25