Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-35469

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-16

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

71/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

spdystream library versions 0.5.0 and below have a memory allocation vulnerability in the SPDY/3 frame parser. The parser uses unchecked 32-bit values from SETTINGS frames, header counts, and header field sizes as allocation sizes without bounds validation. Since SPDY header blocks are zlib-compressed, small payloads can decompress to large attacker-controlled allocation values, enabling a remote attacker to exhaust process memory with a single crafted frame.

MitigationUpgrade spdystream to version 0.5.1 or later, which contains bounds checking validation before memory allocation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if spdystream library is in use

Search your codebase or dependencies for spdystream imports (e.g., 'github.com/docker/spdystream' in Go projects, or check vendor directories, go.mod, or dependency lock files)

Affected if The spdystream library is present in your dependencies or codebase
Determine installed spdystream version

Inspect your dependency manifest (go.mod, go.sum, vendor.conf, or similar) for the spdystream version entry; run 'go list -m all | grep spdystream' if using Go

Affected if The version is 0.5.0 or lower, or no version is specified indicating an old release
Confirm SPDY/3 protocol is enabled

Review your application configuration and code for SPDY/3 protocol usage; look for spdystream.NewConnection or similar SPDY server/client initialization with default settings

Affected if Your application creates SPDY/3 connections using spdystream without custom frame handling
Check if untrusted SPDY traffic can reach the service

Review network exposure: determine if SPDY endpoints accept external connections or only trusted internal clients; inspect firewall rules and service binding addresses

Affected if SPDY connections from untrusted or internet-facing sources are allowed

You are affected if your environment uses spdystream version 0.5.0 or below and accepts SPDY/3 connections, especially from untrusted sources, as the lack of bounds validation on decompressed header sizes can be exploited to trigger memory exhaustion.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade spdystream to version 0.5.1 or later, which contains bounds checking validation before memory allocation.

Recommended fix High confidence

spdystream v0.5.1

Update the spdystream dependency in your project to version 0.5.1 or later
Run go mod tidy to update go.mod and go.sum files
Rebuild and redeploy the service that uses spdystream
Verify the service starts successfully and handles SPDY connections without memory issues

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation2.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,120

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-35469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35469 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-35469?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.7%

Remediation

Need this fixed?

Have this fixed 12 hrs · Moderate

Typical engagement from $2,120

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-35469 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References