CVE-2026-95839: containerd · Uncaught Exception
Affects containerdSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 2.4.2 : patch containerd soon.
Data as of 16 Nov 2026, 20:20 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 7.1 |
|---|
- Patch
- Available – fixed in 2.4.2, 2.3.7, 2.2.10
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade containerd to 2.4.2, 2.3.7 or 2.2.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| containerdcontainerd | Affected
| Fixed in
|
| containerdcontainerd | Affected
| Fixed in
|
| containerdcontainerd | Affected
| Fixed in
|
AI-suggested
Users should upgrade containerd to versions 2.2.10, 2.3.7, or 2.4.2 or later, where this issue is fixed. No other mitigation or workaround is indicated. Applying the official fixes will prevent the daemon crashes caused by malformed image manifests.
Description
CVE-2026-95839 is a vulnerability in containerd, an open-source container runtime, affecting versions from 2.2.0 up to but not including 2.2.10, 2.3.7, and 2.4.2. The flaw occurs when processing image manifests with a child descriptor containing a specific annotation and a malformed digest, which can cause an unrecovered panic and crash the containerd daemon. In Kubernetes environments, this can lead to repeated crashes due to kubelet retries, disrupting container operations on worker nodes. The issue is fixed in containerd versions 2.2.10, 2.3.7, and 2.4.2.
References
- github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f (opens in a new tab)
- github.com/containerd/containerd/commit/20a3b31390653d7a83fdaeb0c318b01a263c9d9a (opens in a new tab)
- github.com/containerd/containerd/commit/2181d7baa2a303ea2082e5c0f1a7697787b61ef2 (opens in a new tab)
- github.com/containerd/containerd/commit/2455fec2f7bfa63adb1f993c63ba0cea9cdedb8c (opens in a new tab)
- github.com/containerd/containerd/commit/a2eb01f667b320b00ec218216f26f7b79197d4cd (opens in a new tab)
- github.com/containerd/containerd/releases/tag/v2.2.10 (opens in a new tab)
- github.com/containerd/containerd/releases/tag/v2.3.7 (opens in a new tab)
- github.com/containerd/containerd/releases/tag/v2.4.2 (opens in a new tab)