Skip to content
Threat Brief

← All advisories

CVE-2026-95839

High 7.1No known exploitationFix available

containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor

Vendor advisory: GHSA-vwhp-8p66-mq4f

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 35% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

containerd is an open-source container runtime. From 2.2.0 until 2.2.10, 2.3.7, and 2.4.2, image manifest processing through the transfer service can encounter a child descriptor containing the io.containerd.manifest.subject annotation and a malformed digest. Pulling or importing such an image, including through a default CRI PullImage request, can trigger an unrecovered panic and crash the containerd daemon. In Kubernetes, kubelet retries can repeatedly trigger the crash and disrupt container operations on the worker node. This issue is fixed in versions 2.2.10, 2.3.7, and 2.4.2.

Weakness: CWE-248

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl4 docker-buildx 0.37.2-2.azl4 on Azure Linux 4.0Not documented0:0.38.2-2.azl4Microsoft MSRC
containerdcontainerd>= 2.2.0, < 2.2.10Not documentedCVE Program
containerdcontainerd>= 2.3.0, < 2.3.7Not documentedCVE Program
containerdcontainerd>= 2.4.0, < 2.4.2Not documentedCVE Program
gogithub.com/containerd/containerd/v2from 2.2.0 before 2.2.102.2.10GitHub Advisory Database
gogithub.com/containerd/containerd/v2from 2.3.0 before 2.3.72.3.7GitHub Advisory Database
gogithub.com/containerd/containerd/v2from 2.4.0 before 2.4.22.4.2GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references