Memory Leak in Mirantis Container Runtime (MCR) running in FIPS mode causes a Denial of Service
Priority LOW 35CWE-401Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-401.
Summary
When running with FIPS mode enabled, Mirantis Container Runtime 20.10.8 leaks memory during TLS Handshakes which could be abused to cause a denial of service.
Why it matters now
EPSS 0.00933 60th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2021-23218
- 2026-10-03 Alias added: GHSA-3v69-r3x2-qgp5
References
Sources
- CVE-2021-23218 · CVE Program
- CVE-2021-23218 · NVD
- FIRST EPSS
- GHSA-3v69-r3x2-qgp5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences