Allocation of Resources Without Limits or Throttling The advisory has been revoked - it doesn't affect any version of package istio-pilot-agent-1.28-compat (opens in a new tab)

Threat Intelligence

Trending on 𝕏

0.66% (47^th 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-MINIMOSLATEST-ISTIOPILOTAGENT128COMPAT-16326483
published1 May 2026
disclosed16 Apr 2026

Report a new vulnerability Found a mistake?

Introduced: 16 Apr 2026

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

Amendment

The Minimos security team deemed this advisory irrelevant for Minimos:latest.

NVD Description

Note: Versions mentioned in the description apply only to the upstream istio-pilot-agent-1.28-compat package and not the istio-pilot-agent-1.28-compat package as distributed by Minimos.

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.