containerd· ()

This monthVendor security release

containerd security releases: 2.4.1, 2.3.6, 2.2.9, 2.0.13, 1.7.36

What
containerd published security fixes. Upgrade to 2.4.1 / 2.3.6 / 2.2.9 / 2.0.13 / 1.7.36 (whichever matches your branch). Fixes 1 CVE. Vendor severity: Medium.
Fix
Upgrade to 2.4.12.3.62.2.92.0.131.7.36
Why this tier
Vendor security release for server software (most severe: CVE-2026-53493).
Exploited
Not known to be exploited · highest EPSS 0.4%
Share this

What to do now#

  1. Check whether you run an affected containerd version:
    containerd --version
  2. Upgrade to the fixed release for your branch: 2.4.1, 2.3.6, 2.2.9, 2.0.13, 1.7.36.Vendor announcement
  3. On Kubernetes, containerd comes with the node image or OS package: roll nodes onto a patched image.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2026-53493:Debian · Ubuntu · Red Hat · Alpine

CVEs 1#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-53493Routine6.9 (v4.0)0.4%Nonone

Sources#

Built from containerd: GitHub Security Advisories (containerd/containerd), checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Linux distribution packages#

Running the distro’s package? These are the versions that carry the fix.

Linux distribution packages CVE-2026-53493

DistroReleasePackageStatus
Debian13 trixiecontainerdNo fix yet
12 bookwormcontainerdNo fix yet
Ubuntu (+3 more packages)22.04 LTScontainerdNo fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Something wrong on this page?
Anonymous. Reports are checked against the primary source.