CVE-2026-50195: containerd: CRI checkpoint import allows local image tag poisoning
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: containerd (Debian:14) 2.1.9+ds1-1; github.com/containerd/containerd/v2 (Go) 2.1.9, 2.2.5, 2.3.2; trivy (openSUSE:Leap 16.0) 0.71.2-160000.1.1.
Low priority for now. Upgrade to containerd (Debian:14) 2.1.9+ds1-1; github.com/containerd/containerd/v2 (Go) 2.1.9, 2.2.5, 2.3.2; trivy (openSUSE:Leap 16.0) 0.71.2-160000.1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
- Published
- Jul 1, 2026
- Updated
- Jul 2, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-345
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | containerd | cpe:2.3:a:linuxfoundation:containerd |
Using containerd? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linuxfoundation containerd2.1.0 and later · before 2.1.9
- linuxfoundation containerd2.2.0 and later · before 2.2.5
- linuxfoundation containerd2.3.0 and later · before 2.3.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
containerd containerd
- >= 2.1.0, < 2.1.9, >= 2.2.0, < 2.2.5, >= 2.3.0, < 2.3.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | containerd | before 2.1.9+ds1-1 | 2.1.9+ds1-1 |
| Go | github.com/containerd/containerd | from 0 | — |
| Go | github.com/containerd/containerd/v2 | from 2.1.0 · before 2.1.9 | 2.1.9 |
| Go | github.com/containerd/containerd/v2 | from 2.2.0 · before 2.2.5 | 2.2.5 |
| Go | github.com/containerd/containerd/v2 | from 2.3.0 · before 2.3.2 | 2.3.2 |
| openSUSE:Leap 16.0 | trivy | before 0.71.2-160000.1.1 | 0.71.2-160000.1.1 |
| openSUSE:Tumbleweed | trivy | before 0.71.2-1.1 | 0.71.2-1.1 |
| Red Hat:hummingbird:1 | trivy | before 0:0.72.0-0.1.hum1 | 0:0.72.0-0.1.hum1 |
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23648Insecure handling of image volumes in containerd CRI plugin38Monitor
- CVE-2026-53488containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull37Monitor
- CVE-2021-43816Improper Preservation of Permissions in containerd37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-46680Jul 1, 2026 · containerd user ID handling bypass allows runAsNonRoot evasion29Monitor
- ← EarlierCVE-2026-47262Jul 1, 2026 · containerd image-triggered runtime DoS via unbounded group parsing21Monitor
- Later →CVE-2026-53489Jul 1, 2026 · containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:containerd | 2.1.9+ds1-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/containerd/containerd/v2 | 2.1.9 | Package registry (OSV) |
| Go:github.com/containerd/containerd/v2 | 2.2.5 | Package registry (OSV) |
| Go:github.com/containerd/containerd/v2 | 2.3.2 | Package registry (OSV) |
| opensuse:trivy | 0.71.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:trivy | 0:0.72.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.