Resource Exhaustion Affecting k3s-1.34 package, versions <1.34.11.1-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (35th 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-WOLFILATEST-K3S134-19512063
  • published3 Sept 2026
  • disclosed1 Sept 2026

Introduced: 1 Sep 2026

NewCVE-2026-84304  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade Wolfi k3s-1.34 to version 1.34.11.1-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream k3s-1.34 package and not the k3s-1.34 package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.