Search threats, CVEs… ⌘K
← Back to CVE intelligence
CVE intelligence

CVE-2026-35469

Vulnerability intelligence

Published Apr 16, 2026Sources checked Nov 11, 2026
6.5MEDIUMCVSS out of 10
What this means

Review the available evidence

CVE-2026-35469 and is rated Medium severity with a CVSS score of 6.5. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

Vendor revision: Sep 25, 2026
Vendor remediation details

CBL-Mariner Releases

Vendor-listed releases

  • 2.0.0-19
  • 1.12.15-7
  • 1.62.0-4
  • 1.32.0-5
  • 0.14.0-12
  • 2.27.0-10
  • 2.14.1-12
  • 1.30.10-23
  • 1.7.1-3
  • 1.15.0-4
  • 1.7.7-12
CISA KEVNot listedBased on the latest collected catalog
EPSS0.7%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-35469?

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.

Source: NVD