Memory Leak Affecting k3s package, versions <1.34.1.1-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.01% (2nd 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 Learn

Learn about Memory Leak vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-K3S-13916051
  • published12 Nov 2025
  • disclosed7 Nov 2025

Introduced: 7 Nov 2025

NewCVE-2025-64329  (opens in a new tab)
CWE-401  (opens in a new tab)

How to fix?

Upgrade Chainguard k3s to version 1.34.1.1-r3 or higher.

NVD Description

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

containerd is an open-source container runtime. Versions 1.7.28 and below, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4, and 2.2.0-beta.0 through 2.2.0-rc.1 contain a bug in the CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. To workaround this vulnerability, users can set up an admission controller to control accesses to pods/attach resources.