Allocation of Resources Without Limits or Throttling Affecting kubernetes1.24-client package, versions <1.24.17-150500.3.33.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.66% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-KUBERNETES124CLIENT-17319985
  • published12 Jun 2026
  • disclosed10 Jun 2026

Introduced: 10 Jun 2026

CVE-2026-35469  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 kubernetes1.24-client to version 1.24.17-150500.3.33.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubernetes1.24-client package and not the kubernetes1.24-client package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

References

CVSS Base Scores

version 3.1