Host memory exhaustion via canceled Attach streams
Published Nov 7, 2025 · Updated Nov 7, 2025
Memory exhaustion in containerd CRI Attach allows local users to interrupt the host runtime through repeated attach requests. ContainerIO.Attach waits only for each stream's close channel, so a canceled client leaves the goroutine and stdout and stderr write-group entries allocated. Access to Kubernetes pods/attach is required; repeated calls progressively consume host memory and can deny container runtime service.
Summary
What happened
Memory exhaustion in containerd CRI Attach allows local users to interrupt the host runtime through repeated attach requests. ContainerIO.Attach waits only for each stream's close channel, so a canceled client leaves the goroutine and stdout and stderr write-group entries allocated. Access to Kubernetes pods/attach is required; repeated calls progressively consume host memory and can deny container runtime service.
The record
- CVE
- CVE-2025-64329
- Published
- Nov 7, 2025
- Updated
- Nov 7, 2025
- Vendor
- containerd
- Product
- containerd
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 7, 2025CVE publishedPublication date reported by the CVE source.
- Nov 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.29
- Affected versionversion=< 2.0.7
- Affected versionversion=>= 2.1.0-beta.0, < 2.1.5
- Affected versionversion=>= 2.2.0-beta.0, < 2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo