Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-50195: containerd is an open-source container runtime

45
This month
CRITICAL 9.9WATCHLISTUPGRADE

CVE-2026-50195 is a critical-severity flaw (CVSS 9.9) affecting containerd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local i

Why this priority

  • Critical severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.9 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 77%)
CISA exploited listNo
WeaknessCWE-345, CWE-829
Published2026-07-01
Last modified2026-07-02
Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Share: LinkedIn · X · Reddit

Last updated 2026-07-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

linuxfoundation containerd UPGRADE
Affected: >= 2.1.0 and < 2.1.9 · >= 2.2.0 and < 2.2.5 · >= 2.3.0 and < 2.3.2
Fixed in: 2.1.9, 2.2.5, 2.3.2
Safe to downgrade to: a release before 2.1.0
1. Check installed version
apt-cache policy containerd || rpm -q containerd || containerd --version
2. UPGRADE to 2.1.9 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade containerd
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade containerd
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)
apt-cache madison containerd sudo apt install containerd=<VERSION_BEFORE_2.1.0> sudo apt-mark hold containerd
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list containerd sudo dnf downgrade containerd-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add containerd
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-50195?

containerd: upgrade to 2.1.9, 2.2.5, 2.3.2. Exact commands for each OS are on this page.

Is CVE-2026-50195 being exploited?

CVE-2026-50195 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-50195 affect?

CVE-2026-50195 affects containerd. Severity is critical (CVSS 9.9). containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's conf

How urgent is CVE-2026-50195?

Priority 45/100. Critical severity; On your watchlist

Software pages

containerd and runc vulnerabilities · Check Point vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.