CVE-2026-50195
containerd: CRI checkpoint import allows local image tag poisoning
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.6
containerd: CRI checkpoint import allows local image tag poisoning
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.
- Record
CVE-2026-50195- CVSS 4.0
- 5.6 Medium
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 - Weakness
- CWE-345, CWE-829
- Updated
- 2026-11-02
EUVDEUVD-2026-41108
5.6
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.
- Record
EUVD-2026-41108- CVSS 4.0
- 5.6 Medium
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 - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-cvxm-645q-p574
5.6
containerd: CRI checkpoint import allows local image tag poisoning
Impact
containerd's CRI checkpoint import process contains a vulnerability 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.
Patches
This bug has been fixed in the following containerd versions:
- 2.3.2
- 2.2.5
- 2.1.9
Users should update to these versions to resolve the issue.
Workarounds
Users should only allow trusted images to be pulled.
Credits
The containerd project would like to thank Henry Beberman (@hbeberman) of Microsoft, the GKE Security Team using Gemini, Anthropic Research, in collaboration with Claude, and Robert Prast (@robertprast) who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue in containerd
- Email us at [email protected]
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [email protected]
- Record
GHSA-cvxm-645q-p574- CVSS 4.0
- 5.6 Medium
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 - CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-345, CWE-829
- Updated
- 2026-11-02
NVD
5.6
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.
- Record
CVE-2026-50195- CVSS 4.0
- 5.6 Medium
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 - CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-345, CWE-829
- Updated
- 2026-11-02
OSVALPINE-CVE-2026-50195
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 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.
- Record
ALPINE-CVE-2026-50195- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-03
OSVBELL-CVE-2026-50195
9.9
- Record
BELL-CVE-2026-50195- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
Show 11 moreShow less
OSV
5.6
containerd: CRI checkpoint import allows local image tag poisoning
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.
- Record
CVE-2026-50195- CVSS 4.0
- 5.6 Medium
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 - Weakness
- CWE-345, CWE-829
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-50195
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 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.
- Record
DEBIAN-CVE-2026-50195- CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-cvxm-645q-p574
5.6
containerd: CRI checkpoint import allows local image tag poisoning
Impact
containerd's CRI checkpoint import process contains a vulnerability 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.
Patches
This bug has been fixed in the following containerd versions:
- 2.3.2
- 2.2.5
- 2.1.9
Users should update to these versions to resolve the issue.
Workarounds
Users should only allow trusted images to be pulled.
Credits
The containerd project would like to thank Henry Beberman (@hbeberman) of Microsoft, the GKE Security Team using Gemini, Anthropic Research, in collaboration with Claude, and Robert Prast (@robertprast) who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue in containerd
- Email us at [email protected]
To report a security issue in containerd:
- Report a new vulnerability
- Email us at [email protected]
- Record
GHSA-cvxm-645q-p574- CVSS 4.0
- 5.6 Medium
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 - CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-345, CWE-829
- Updated
- 2026-11-02
OSVRHSA-2026:35111
8.8
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- Record
RHSA-2026:35111- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-50195
5.6
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.
- Record
UBUNTU-CVE-2026-50195- CVSS 4.0
- 5.6 Medium
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 - CVSS 3.1
- 9.9 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVAZL-90164 No score
CVE-2026-50195 affecting package containerd2 for versions less than 2.2.4-3
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.
- Record
AZL-90164- Updated
- 2026-11-02
OSVGO-2026-5338 No score
containerd: CRI checkpoint import allows local image tag poisoning in github.com/containerd/containerd
containerd: CRI checkpoint import allows local image tag poisoning in github.com/containerd/containerd
- Record
GO-2026-5338- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11102-1 No score
trivy-0.71.2-1.1 on GA media
These are all security issues fixed in the trivy-0.71.2-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11102-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21072-1 No score
Security update for trivy
This update for trivy fixes the following issues
Update to version 0.71.2:
- CVE-2026-44740: github.com/go-git/go-billy/v5: improper input handling in many components can lead to DoS via infinite loops, panics or resource consumption (bsc#1267268).
- CVE-2026-46680: github.com/containerd/containerd/v2/pkg/oci: containerd user ID handling bypass allows runAsNonRoot evasion (bsc#1268356).
- CVE-2026-47262: github.com/containerd/containerd/v2/pkg/oci: Denial of Service (DoS) condition via a maliciously crafted image (bsc#1268440).
- CVE-2026-50195: containerd: fails to validate the image references specified within a checkpoint image's configuration (bsc#1268399).
- CVE-2026-53488: containerd: CRI plugin propagates labels from an image config to a container without validation (bsc#1268400).
- CVE-2026-53489: containerd: CRI plugin restores container.log from a checkpoint image without validating a symlinked path (bsc#1268404).
- CVE-2026-53492: containerd: improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration (bsc#1268403).
Changes for trivy:
- release: v0.71.2 [release/v0.71] (#10871)
- fix(deps): bump alpine to 3.24.1 [backport: release/v0.71] (#10870)
- chore(deps): bump the common group with 4 updates [backport: release/v0.71] (#10867)
- fix(oci): validate artifact filename
- fix: forward ospkg detector options through ospkg.NewScanner
- fix(vex): load VEX documents from within the repository directory
- fix: surface the original analysis error instead of context cancellation
- ci: expect GitHub App bot as backport PR author
- Record
openSUSE-SU-2026:21072-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVROOT-APP-GOBINARY-CVE-2026-50195 No score
CVE-2026-50195 in github.com/containerd/containerd - Patched by Root
Root has patched CVE-2026-50195 in the github.com/containerd/containerd package for Root:Go. Multiple fixed versions available.
- Record
ROOT-APP-GOBINARY-CVE-2026-50195- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/containerd/containerd/v2Go |
2.1.0 up to 2.1.9 | 2.1.9 |
github.com/containerd/containerd/v2Go |
2.2.0 up to 2.2.5 | 2.2.5 |
github.com/containerd/containerd/v2Go |
2.3.0 up to 2.3.2 | 2.3.2 |
containerdAlpine:v3.24 |
2.1.0 up to 2.3.2-r0 | 2.3.2-r0 |
containerd2Azure Linux:3 |
before 2.2.4-3 | 2.2.4-3 |
containerdAlpaquita:25 |
2.1.1-r0 up to 2.2.8-r0 | 2.2.8-r0 |
containerdAlpaquita:stream |
1.7.2-r1 up to 2.3.2-r0 | 2.3.2-r0 |
containerdDebian:14 |
before 2.1.9+ds1-1, plus listed versions 1.7.24~ds1-101.7.24~ds1-61.7.24~ds1-71.7.24~ds1-81.7.24~ds1-9 Show 8 moreShow less2.1.4~ds2-22.1.4~ds2-32.1.4~ds2-42.1.4~ds2-52.1.4~ds2-62.1.4~ds2-72.1.4~ds2-82.1.6+ds1-1 |
2.1.9+ds1-1 |
github.com/containerd/containerdGo |
All versions | None known |
github.com/containerd/containerd/v2Go |
2.1.0 up to 2.1.9, 2.2.0 up to 2.2.5, 2.3.0 up to 2.3.2 | 2.1.92.2.52.3.2 |
Show 12 moreShow less
| Package | Affected | Fixed |
|---|---|---|
trivyRed Hat:hummingbird:1 |
before 0:0.72.0-0.1.hum1 | 0:0.72.0-0.1.hum1 |
github.com/containerd/containerdRoot:Go |
before v1.7.33-aikido.2 | v1.7.33-aikido.2 |
rootio-github.com/containerd/containerdRoot:Go |
before v1.7.33-root.io.2 | v1.7.33-root.io.2 |
containerd-appUbuntu:22.04:LTS |
before 2.2.1-0ubuntu1~22.04.2, plus listed versions 1.7.2-0ubuntu1~22.04.11.7.12-0ubuntu2~22.04.11.7.24-0ubuntu1~22.04.11.7.24-0ubuntu1~22.04.21.7.27-0ubuntu1~22.04.11.7.28-0ubuntu1~22.04.12.2.1-0ubuntu1~22.04.1 |
2.2.1-0ubuntu1~22.04.2 |
containerd-appUbuntu:24.04:LTS |
before 2.2.1-0ubuntu1~24.04.3, plus listed versions 1.7.2-0ubuntu21.7.12-0ubuntu11.7.12-0ubuntu21.7.12-0ubuntu31.7.12-0ubuntu4 Show 9 moreShow less1.7.12-0ubuntu4.11.7.19-0ubuntu1~24.04.11.7.19+really1.7.12-0ubuntu4.21.7.24-0ubuntu1~24.04.11.7.24-0ubuntu1~24.04.21.7.27-0ubuntu1~24.04.11.7.28-0ubuntu1~24.04.11.7.28-0ubuntu1~24.04.22.2.1-0ubuntu1~24.04.2 |
2.2.1-0ubuntu1~24.04.3 |
containerd-appUbuntu:25.10 |
before 2.2.1-0ubuntu1~25.10.2, plus listed versions 2.0.2-0ubuntu22.0.5-0ubuntu12.1.3-0ubuntu22.1.3-0ubuntu32.1.3-0ubuntu3.12.2.1-0ubuntu1~25.10.1 |
2.2.1-0ubuntu1~25.10.2 |
containerd-stableUbuntu:25.10 |
before 2.1.6-0ubuntu1~25.10.2, plus listed versions 2.1.3-0ubuntu12.1.6-0ubuntu1~25.10.1 |
2.1.6-0ubuntu1~25.10.2 |
containerd-appUbuntu:26.04:LTS |
before 2.2.2-0ubuntu1.1, plus listed versions 2.1.3-0ubuntu32.2.1-0ubuntu12.2.2-0ubuntu1 |
2.2.2-0ubuntu1.1 |
containerd-stableUbuntu:26.04:LTS |
before 2.2.2-0ubuntu1.1, plus listed versions 2.1.3-0ubuntu12.1.5-0ubuntu12.2.1-0ubuntu12.2.2-0ubuntu1 |
2.2.2-0ubuntu1.1 |
trivyopenSUSE:Tumbleweed |
before 0.71.2-1.1 | 0.71.2-1.1 |
trivyopenSUSE:Leap 16.0 |
before 0.71.2-160000.1.1 | 0.71.2-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-50195 is a medium vulnerability (CVSS 5.6) in Containerd, published June 19, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.30%, the 23rd percentile. Fixed in github.com/containerd/containerd/v2 2.1.9.
References
github.com/containerd/containerd/security/advisories/GHSA-cvxm-645q-p574
nvd.nist.gov/vuln/detail/CVE-2026-50195
github.com/advisories/GHSA-cvxm-645q-p574
security.alpinelinux.org/vuln/CVE-2026-50195
docs.bell-sw.com/security/cves/CVE-2026-50195
github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50195.json
Show 194 moreShow less
security-tracker.debian.org/tracker/CVE-2026-50195
github.com/containerd/containerd
access.redhat.com/errata/RHSA-2026:35111
access.redhat.com/security/cve/CVE-2026-46680
access.redhat.com/security/cve/CVE-2026-47262
access.redhat.com/security/cve/CVE-2026-53488
access.redhat.com/security/updates/classification
images.redhat.com
access.redhat.com/security/cve/CVE-2026-50195
access.redhat.com/security/cve/CVE-2026-32285
access.redhat.com/security/cve/CVE-2026-44740
access.redhat.com/security/cve/CVE-2026-41506
access.redhat.com/security/cve/CVE-2026-48702
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35111.json
bugzilla.redhat.com/show_bug.cgi?id=2451846
cve.org/CVERecord?id=CVE-2026-32285
nvd.nist.gov/vuln/detail/CVE-2026-32285
github.com/buger/jsonparser/issues/275
github.com/golang/vulndb/issues/4514
pkg.go.dev/vuln/GO-2026-4514
bugzilla.redhat.com/show_bug.cgi?id=2468126
cve.org/CVERecord?id=CVE-2026-41506
nvd.nist.gov/vuln/detail/CVE-2026-41506
github.com/go-git/go-git/releases/tag/v5.18.0
github.com/go-git/go-git/releases/tag/v6.0.0-alpha.2
github.com/go-git/go-git/security/advisories/GHSA-3xc5-wrhm-f963
bugzilla.redhat.com/show_bug.cgi?id=2483894
cve.org/CVERecord?id=CVE-2026-44740
nvd.nist.gov/vuln/detail/CVE-2026-44740
github.com/go-git/go-billy/releases/tag/v5.9.0
github.com/go-git/go-billy/releases/tag/v6.0.0-alpha.1
github.com/go-git/go-billy/security/advisories/GHSA-m3xc-h892-ggx6
bugzilla.redhat.com/show_bug.cgi?id=2496104
cve.org/CVERecord?id=CVE-2026-46680
nvd.nist.gov/vuln/detail/CVE-2026-46680
github.com/containerd/containerd/security/advisories/GHSA-fqw6-gf59-qr4w
bugzilla.redhat.com/show_bug.cgi?id=2496126
cve.org/CVERecord?id=CVE-2026-47262
nvd.nist.gov/vuln/detail/CVE-2026-47262
github.com/containerd/containerd/security/advisories/GHSA-jpcc-p29g-p8mq
bugzilla.redhat.com/show_bug.cgi?id=2499685
cve.org/CVERecord?id=CVE-2026-48702
nvd.nist.gov/vuln/detail/CVE-2026-48702
github.com/sigstore/rekor/security/advisories/GHSA-47q9-m4ww-924m
bugzilla.redhat.com/show_bug.cgi?id=2496128
cve.org/CVERecord?id=CVE-2026-50195
bugzilla.redhat.com/show_bug.cgi?id=2495815
cve.org/CVERecord?id=CVE-2026-53488
nvd.nist.gov/vuln/detail/CVE-2026-53488
github.com/containerd/containerd/security/advisories/GHSA-xhf5-7wjv-pqxp
ubuntu.com/security/CVE-2026-50195
ubuntu.com/security/notices/USN-8472-1
ubuntu.com/security/notices/USN-8473-1
suse.com/security/cve/CVE-2026-47262
suse.com/security/cve/CVE-2026-50195
suse.com/security/cve/CVE-2026-53488
suse.com/security/cve/CVE-2026-53489
suse.com/security/cve/CVE-2026-53492
bugzilla.suse.com/1267268
bugzilla.suse.com/1268356
bugzilla.suse.com/1268399
bugzilla.suse.com/1268400
bugzilla.suse.com/1268403
bugzilla.suse.com/1268404
bugzilla.suse.com/1268440
suse.com/security/cve/CVE-2026-44740
suse.com/security/cve/CVE-2026-46680
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
suse.com/security/cve/CVE-2016-11068
suse.com/security/cve/CVE-2016-11069
suse.com/security/cve/CVE-2016-11070
suse.com/security/cve/CVE-2016-11071
suse.com/security/cve/CVE-2016-11072
suse.com/security/cve/CVE-2016-11073
suse.com/security/cve/CVE-2016-11074
suse.com/security/cve/CVE-2016-11075
suse.com/security/cve/CVE-2016-11076
suse.com/security/cve/CVE-2016-11077
suse.com/security/cve/CVE-2016-11078
suse.com/security/cve/CVE-2016-11079
suse.com/security/cve/CVE-2016-11080
suse.com/security/cve/CVE-2016-11081
suse.com/security/cve/CVE-2016-11082
suse.com/security/cve/CVE-2016-11083
suse.com/security/cve/CVE-2016-11084
suse.com/security/cve/CVE-2017-18870
suse.com/security/cve/CVE-2017-18871
suse.com/security/cve/CVE-2017-18872
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18874
suse.com/security/cve/CVE-2017-18875
suse.com/security/cve/CVE-2017-18876
suse.com/security/cve/CVE-2017-18877
suse.com/security/cve/CVE-2017-18878
suse.com/security/cve/CVE-2017-18879
suse.com/security/cve/CVE-2017-18883
suse.com/security/cve/CVE-2017-18884
suse.com/security/cve/CVE-2017-18885
suse.com/security/cve/CVE-2017-18886
suse.com/security/cve/CVE-2017-18887
suse.com/security/cve/CVE-2017-18888
suse.com/security/cve/CVE-2017-18889
suse.com/security/cve/CVE-2017-18890
suse.com/security/cve/CVE-2017-18891
suse.com/security/cve/CVE-2017-18892
suse.com/security/cve/CVE-2017-18893
suse.com/security/cve/CVE-2017-18894
suse.com/security/cve/CVE-2017-18895
suse.com/security/cve/CVE-2017-18896
suse.com/security/cve/CVE-2017-18897
suse.com/security/cve/CVE-2017-18898
suse.com/security/cve/CVE-2017-18900
suse.com/security/cve/CVE-2017-18901
suse.com/security/cve/CVE-2017-18902
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18904
suse.com/security/cve/CVE-2017-18905
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
suse.com/security/cve/CVE-2017-18909
suse.com/security/cve/CVE-2017-18911
suse.com/security/cve/CVE-2017-18912
suse.com/security/cve/CVE-2017-18915
suse.com/security/cve/CVE-2017-18916
suse.com/security/cve/CVE-2017-18917
suse.com/security/cve/CVE-2017-18918
suse.com/security/cve/CVE-2018-21258
suse.com/security/cve/CVE-2019-8400
suse.com/security/cve/CVE-2021-25320
suse.com/security/cve/CVE-2022-45786
suse.com/security/cve/CVE-2023-26154
suse.com/security/cve/CVE-2023-32199
suse.com/security/cve/CVE-2023-34620
suse.com/security/cve/CVE-2023-43630
suse.com/security/cve/CVE-2023-43631
suse.com/security/cve/CVE-2023-43632
suse.com/security/cve/CVE-2023-43633
suse.com/security/cve/CVE-2023-43634
suse.com/security/cve/CVE-2023-43635
suse.com/security/cve/CVE-2023-43636
suse.com/security/cve/CVE-2023-43637
suse.com/security/cve/CVE-2023-47108
suse.com/security/cve/CVE-2024-12886
suse.com/security/cve/CVE-2024-21635
suse.com/security/cve/CVE-2024-25621
suse.com/security/cve/CVE-2024-41260
suse.com/security/cve/CVE-2024-41265
suse.com/security/cve/CVE-2024-44905
suse.com/security/cve/CVE-2024-52284
suse.com/security/cve/CVE-2024-53412
suse.com/security/cve/CVE-2024-58259
suse.com/security/cve/CVE-2024-58260
suse.com/security/cve/CVE-2024-58267
suse.com/security/cve/CVE-2024-58269
suse.com/security/cve/CVE-2024-6717
suse.com/security/cve/CVE-2025-0426
suse.com/security/cve/CVE-2025-10543
suse.com/security/cve/CVE-2025-10545
suse.com/security/cve/CVE-2025-10630
suse.com/security/cve/CVE-2025-10678
suse.com/security/cve/CVE-2025-10954
suse.com/security/cve/CVE-2025-11374
suse.com/security/cve/CVE-2025-11375
suse.com/security/cve/CVE-2025-11393
suse.com/security/cve/CVE-2025-11579
suse.com/security/cve/CVE-2025-11621
suse.com/security/cve/CVE-2025-11776
suse.com/security/cve/CVE-2025-11777
suse.com/security/cve/CVE-2025-11794
suse.com/security/cve/CVE-2025-12044
suse.com/security/cve/CVE-2025-12419
suse.com/security/cve/CVE-2025-12421
suse.com/security/cve/CVE-2025-12559
suse.com/security/cve/CVE-2025-12689
suse.com/security/cve/CVE-2025-12756
suse.com/security/cve/CVE-2025-13281
suse.com/security/cve/CVE-2025-13324
suse.com/security/cve/CVE-2025-13352
suse.com/security/cve/CVE-2025-13353
suse.com/security/cve/CVE-2025-13357
suse.com/security/cve/CVE-2025-13425
suse.com/security/cve/CVE-2025-13523
suse.com/security/cve/CVE-2025-13767
suse.com/security/cve/CVE-2025-13821
suse.com/security/cve/CVE-2025-13870
suse.com/security/cve/CVE-2025-13888
suse.com/security/cve/CVE-2025-14273
suse.com/security/cve/CVE-2025-14350
suse.com/security/cve/CVE-2025-14435
suse.com/security/cve/CVE-2025-14443
suse.com/security/cve/CVE-2025-14525
Left out here: 1,601 references and the rest of 1 source description. The JSON record has them.