CVE-2026-50195: containerd Insufficient Data Authenticity
CVE-2026-50195 is a critical insufficient data authenticity vulnerability in containerd, published in the National Vulnerability Database (NVD) on July 1, 2026. It carries a CVSS v3.1 base score of 9.9 (Critical). According to its CVSS vector, it can be exploited over the network, needs low privileges and no user interaction.
What is CVE-2026-50195?
containerd's checkpoint import allows malicious image injection, compromising pod security.
The NVD description (excerpt) reads:
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 image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one.
NVD maps this issue to CWE-345 (Insufficient Verification of Data Authenticity), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).
Affected versions and packages
NVD's CPE configuration lists these vulnerable version ranges:
- containerd from 2.1.0 before 2.1.9
- containerd from 2.2.0 before 2.2.5
- containerd from 2.3.0 before 2.3.2
Based on those ranges, the first versions that are no longer listed as vulnerable include: 2.1.9, 2.2.5, 2.3.2.
Echo's advisory data tracks 1 package for CVE-2026-50195: github.com/containerd/containerd/v2.
Package versions listed in Echo's advisory data for this CVE (compare them with the versions you run):
- github.com/containerd/containerd/v2: v2.2.4
Severity and CVSS score
A score of 9.9 puts CVE-2026-50195 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to how automated patch SLAs reduce enterprise risk.
Impact: Insufficient Data Authenticity
The CVSS vector rates the impact on confidentiality as high, integrity as high and availability as high. The scope is changed, meaning a successful attack can affect resources beyond the vulnerable component. Exploitation requires low privileges and no user interaction, and the attacker reaches the target over the network.
What this means in practice depends on how containerd is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.
Is CVE-2026-50195 being exploited in the wild?
Known exploitation: CISA KEV
No. As of November 4, 2026, CVE-2026-50195 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). KEV only lists vulnerabilities with confirmed exploitation, so absence from the catalog is not proof that nobody is exploiting the flaw.
EPSS score and percentile
The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a CVE will see exploitation activity in the next 30 days. On November 3, 2026, CVE-2026-50195 had an EPSS score of 0.003, which corresponds to a probability of 0.30%. It sits at the 23rd percentile, which means it is scored as more likely to be exploited than roughly 23% of scored CVEs, placing it below the median of scored CVEs. EPSS is recalculated daily and is a likelihood estimate, not a confirmation, so read it together with KEV status, exposure and CVSS severity.
Attack vector, complexity, privileges and user interaction
Based on the CVSS v3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (source: NVD), this is how an attacker has to approach CVE-2026-50195:
- Attack vector: Network (AV:N): the flaw can be reached remotely over the network, so the attacker does not need to be on the same host or LAN.
- Attack complexity: Low (AC:L): no special conditions are needed, so the attack can be repeated reliably.
- Privileges required: Low (PR:L): the attacker needs a basic, low-privileged account.
- User interaction: None (UI:N): no action by a user is required.
- Scope: Changed (S:C): a successful attack can affect resources beyond the vulnerable component.
Is there a public proof of concept or exploit?
CISA's SSVC assessment recorded in NVD (dated July 1, 2026) lists the exploitation status as "none", which means there was no evidence of active exploitation and no public proof of concept at that time. None of the references in the NVD record is tagged as an exploit. This reflects NVD and CISA records as of November 4, 2026, and public exploit code can appear at any time.
Practical exposure conditions
- Only systems that run an affected version are exposed. Compare the containerd versions in your hosts and container images against the vulnerable ranges listed above.
- The vector is network-based, so containerd deployments that process input from untrusted networks carry the most risk, especially internet-facing ones. Internal-only deployments are still exposed to anyone who can reach them.
- A low-privileged account is enough, so risk grows wherever many users, tenants or customers hold accounts.
- No user has to click or open anything, so the flaw can be triggered without any user action.
- The scope is changed, so a successful attack can reach beyond the vulnerable component.
- CISA's SSVC assessment marks the issue as not automatable, which means attacks are harder to run at scale.
How to fix CVE-2026-50195
- Inventory. Find every host, container image and base image that includes containerd, including the packages listed above (github.com/containerd/containerd/v2).
- Upgrade. Upgrade to 2.1.9, 2.2.5, 2.3.2 or later, the first versions that NVD no longer lists as vulnerable, or to the version your distribution or vendor lists as fixed.
- Rebuild and restart. Rebuild container images and restart the services that load containerd so the patched code is actually used.
- Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2026-50195.
Interim mitigations if you cannot patch immediately
These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.
- Restrict network access to services that use containerd to trusted sources with firewall rules or allow-lists until you can patch.
- Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.
How Echo helps with CVE-2026-50195
Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 1 package (github.com/containerd/containerd/v2). Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters.
Frequently asked questions about CVE-2026-50195
What is CVE-2026-50195?
CVE-2026-50195 is a critical insufficient data authenticity vulnerability in containerd. containerd's checkpoint import allows malicious image injection, compromising pod security. It has a CVSS base score of 9.9.
Which versions are affected by CVE-2026-50195?
NVD lists these vulnerable ranges: containerd from 2.1.0 before 2.1.9; containerd from 2.2.0 before 2.2.5; containerd from 2.3.0 before 2.3.2.
Is CVE-2026-50195 actively exploited?
It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.30%, at the 23rd percentile (November 3, 2026). On public exploit code: CISA's SSVC assessment in NVD (dated July 1, 2026) lists no public proof of concept.
How do I fix CVE-2026-50195?
Upgrade to 2.1.9, 2.2.5, 2.3.2 or later, the first versions that NVD no longer lists as vulnerable, or to the version your distribution or vendor lists as fixed. Then rebuild images, restart affected services and re-scan to confirm the fix.
How severe is CVE-2026-50195?
It is rated Critical with a CVSS base score of 9.9. The vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H means it can be exploited over the network, with low privileges and no user interaction.
What type of weakness is CVE-2026-50195?
NVD classifies it as CWE-345 (Insufficient Verification of Data Authenticity), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).