CVE
containerd denial of service in image digest parsing
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
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.10, 2.3.7, 2.4.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected containerd versions from 2.2.0 until 2.2.10, 2.3.0 until 2.3.7, and 2.4.0 until 2.4.2. Image manifest has a child descriptor carrying the io.containerd.manifest.subject annotation with a malformed digest, processed via the transfer service.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
containerd, an open-source container runtime, has a flaw that lets an attacker with low privileges crash the daemon remotely, without any user action, by getting it to pull or import an image with a malformed digest. In Kubernetes, repeated kubelet retries can keep triggering the crash and disrupt container operations on the worker node.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original 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.
Who should check
Teams running containerd 2.2.x, 2.3.x or 2.4.x that pull or import images, including Kubernetes nodes and Docker hosts using containerd; the advisory says the default CRI PullImage path is affected.
“Affected versions >= 2.2.0, < 2.2.10, >= 2.3.0, < 2.3.7, >= 2.4.0, < 2.4.2”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach17/20Affects Docker (a widely deployed server, runtime, framework or database)
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected containerd versions from 2.2.0 until 2.2.10, 2.3.0 until 2.3.7, and 2.4.0 until 2.4.2. Image manifest has a child descriptor carrying the io.containerd.manifest.subject annotation with a malformed digest, processed via the transfer service.Upgrade to a fixed version: 2.2.10, 2.3.7, 2.4.2.
Workaround: Restrict pod image references to trusted registries (for example, using a Kubernetes ValidatingAdmissionPolicy or admission webhook) and only pull or import images from trusted sources.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-95839 (containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-95839 (entry last updated 2026-11-16):
Affected:
- containerd containerd: from 2.2.0, fixed in 2.2.10; from 2.3.0, fixed in 2.3.7; from 2.4.0, fixed in 2.4.2
Fixed versions: 2.2.10, 2.3.7, 2.4.2.
Conditions (all must be true for the bug to be hit):
- Affected containerd versions from 2.2.0 until 2.2.10, 2.3.0 until 2.3.7, and 2.4.0 until 2.4.2. (source: https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f)
- Image manifest has a child descriptor carrying the io.containerd.manifest.subject annotation with a malformed digest, processed via the transfer service. (source: https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Restrict pod image references to trusted registries (for example, using a Kubernetes ValidatingAdmissionPolicy or admission webhook) and only pull or import images from trusted sources. (source: https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f)
CISA KEV: CVE-2026-95839 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95839 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/containerd/containerd/security/advisories/GHSA-vwhp-8p66-mq4f
- https://github.com/containerd/containerd/commit/20a3b31390653d7a83fdaeb0c318b01a263c9d9a
- https://github.com/containerd/containerd/commit/2181d7baa2a303ea2082e5c0f1a7697787b61ef2
- https://github.com/containerd/containerd/commit/2455fec2f7bfa63adb1f993c63ba0cea9cdedb8c
- https://github.com/containerd/containerd/commit/a2eb01f667b320b00ec218216f26f7b79197d4cd
- https://github.com/containerd/containerd/releases/tag/v2.2.10
- https://github.com/containerd/containerd/releases/tag/v2.3.7
- https://github.com/containerd/containerd/releases/tag/v2.4.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-95839
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95839"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- containerd containerd
From 2.2.0 · fixed in 2.2.10; From 2.3.0 · fixed in 2.3.7; From 2.4.0 · fixed in 2.4.2
Evidence 10
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 7
- Repository
- Repository
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-95839
Is CVE-2026-95839 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A malformed digest in a subject-annotated child descriptor of an image manifest causes an unrecovered panic that crashes the containerd daemon. In Kubernetes, kubelet retries of failed image pulls can repeatedly crash containerd and disrupt container operations on the worker node.Source: github.com
Which versions are affected by CVE-2026-95839?
containerd: from 2.2.0 before 2.2.10; from 2.3.0 before 2.3.7; from 2.4.0 before 2.4.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are containerd 2.2.0 up to but not including 2.2.10, 2.3.0 up to but not including 2.3.7, and 2.4.0 up to but not including 2.4.2. The setup involves image manifests whose child descriptor carries the io.containerd.manifest.subject annotation with a malformed digest, processed through the transfer service. To check a version, run containerd --version on the node.Source: github.com
How do I fix CVE-2026-95839?
Upgrade containerd to 2.2.10, 2.3.7, or 2.4.2, matching your release line. Until then, restrict pod image references to trusted registries, for example with a Kubernetes ValidatingAdmissionPolicy or an admission webhook, and pull or import images only from trusted sources.Source: github.com