Allocation of Resources Without Limits or Throttling Affecting flightctl-cli package, versions <0:1.1.3-1.el10em


Severity

Recommended
high

Based on Red Hat Enterprise Linux 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-RHEL10-FLIGHTCTLCLI-17997932
  • published17 Jul 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

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

How to fix?

Upgrade RHEL:10 flightctl-cli to version 0:1.1.3-1.el10em or higher.
This issue was patched in RHSA-2026:41019.

NVD Description

Note: Versions mentioned in the description apply only to the upstream flightctl-cli package and not the flightctl-cli package as distributed by RHEL. See How to fix? for RHEL:10 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