Skip to main content
VulnerabilityPublished

CVE-2026-95839: containerd · Uncaught Exception

Affects containerdSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
containerdcontainerdAffected
  • >=2.4.0 <2.4.2
Fixed in
  • 2.4.2
containerdcontainerdAffected
  • >=2.3.0 <2.3.7
Fixed in
  • 2.3.7
containerdcontainerdAffected
  • >=2.2.0 <2.2.10
Fixed in
  • 2.2.10

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

Community reviews

Loading reviews…