Vulnerability Database · Debian · containerd · Version
containerd 2.1.4~ds2-3
2.1.4~ds2-3 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 0 Low 0 Unrated 3
-
Database updated 23/Oct/2026
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
containerd 2.1.4~ds2-3 vulnerabilities
4 vulnerabilities cover containerd 2.1.4~ds2-3. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Vulnerability in containerd: CRI CreateContainer Checkpoint Restore Security Flaw | 7.8 high | No fix published | 12 Oct 2026 |
| Critical Directory Traversal Vulnerability in Containerd Package | N/A unrated | No fix published | 12 Oct 2026 |
| High CPU/Memory Usage Vulnerability in containerd - CVE-2026-53493 | N/A unrated | No fix published | 25 Sep 2026 |
| Resource Exhaustion Vulnerability in containerd: OOM Killer Risk | N/A unrated | No fix published | 14 Sep 2026 |
Looking for another version, or everything Vulert holds for containerd?
Questions
About containerd 2.1.4~ds2-3
Is containerd 2.1.4~ds2-3 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover containerd 2.1.4~ds2-3: 0 critical, 1 high, 0 medium and 0 low, plus 3 not yet rated. Each entry above names the fixed version to move to.
How do I monitor containerd for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the containerd version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.