containerd· ()

This monthVendor security release

containerd security releases: 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33

What
containerd published security fixes. Upgrade to 2.3.2 / 2.2.5 / 2.1.9 / 2.0.10 / 1.7.33 (whichever matches your branch). Fixes 5 CVEs. Vendor severity: Medium, Critical, High.
Fix
Upgrade to 2.3.22.2.52.1.92.0.101.7.33
Why this tier
Vendor security release for server software (most severe: CVE-2026-53488).
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.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33.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-47262 (and the other 4 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 5#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-53488Routine9.4 (v4.0)0.2%Nonone
CVE-2026-53492Routine8.4 (v4.0)0.4%Nonone
CVE-2026-53489Routine8.2 (v4.0)0.2%Nonone
CVE-2026-50195Routine5.6 (v4.0)0.3%Nonone
CVE-2026-47262Routine5.3 (v4.0)0.3%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 →

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