Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: containerd 2.2.10, 2.3.7 and 2.4.2 fix a daemon crash from crafted images. High, Docker.

    containerd 2.2.10, 2.3.7 and 2.4.2 fix a daemon crash from crafted images

    Docker

    What's fixed

    CVE-2026-95839 is a denial-of-service flaw in how containerd processes image manifests through the transfer service. A child descriptor that carries the io.containerd.manifest.subject annotation and a malformed digest can trigger an unrecovered panic, which crashes the daemon. Pulling or importing a crafted image is enough, including through a default CRI PullImage request, and the attacker needs only low privileges.

    The record rates it 7.1, HIGH, under CVSS 4.0. On Kubernetes, kubelet retries can repeat the crash and disrupt container operations on the worker node. Affected releases run from 2.2.0 until 2.2.10, 2.3.7 and 2.4.2 on their respective lines. The record gives no exploitation status and no workaround.

    What to do

    Update containerd to 2.2.10, 2.3.7 or 2.4.2, matching your release line, and prioritise Kubernetes worker nodes.

    Product Affected Fixed
    containerd 2.2 line 2.2.0 until 2.2.10 2.2.10
    containerd 2.3 line before 2.3.7 (2.3 line) 2.3.7
    containerd 2.4 line before 2.4.2 (2.4 line) 2.4.2

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion