<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 12:16:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-50195 — containerd: CRI checkpoint import allows local image tag poisoning</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-50195</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; containerd&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;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&amp;#39;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&amp;#39;s identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; containerd&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;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&amp;#39;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&amp;#39;s identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-50195</guid>
    </item>
    <item>
      <title>GHSA-cvxm-645q-p574 — containerd: CRI checkpoint import allows local image tag poisoning</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-cvxm-645q-p574</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd/v2&lt;/p&gt;
&lt;p&gt;## Impact
containerd&amp;#39;s CRI checkpoint import process contains a vulnerability where it fails to validate the image references specified within a checkpoint image&amp;#39;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&amp;#39;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&amp;#39;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&amp;#39;s identity.&lt;/p&gt;
&lt;p&gt;## Patches
This bug has been fixed in the following containerd versions:&lt;/p&gt;
&lt;p&gt;* 2.3.2
* 2.2.5
* 2.1.9&lt;/p&gt;
&lt;p&gt;Users should update to these versions to resolve the issue.
## Workarounds
Users should only allow trusted images to be pulled.&lt;/p&gt;
&lt;p&gt;## 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](https://github.com/containerd/project/blob/main/SECURITY.md).&lt;/p&gt;
&lt;p&gt;## For more information
If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Open an issue in [containerd](https://github.com…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containerd/containerd/v2&lt;/p&gt;
&lt;p&gt;## Impact
containerd&amp;#39;s CRI checkpoint import process contains a vulnerability where it fails to validate the image references specified within a checkpoint image&amp;#39;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&amp;#39;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&amp;#39;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&amp;#39;s identity.&lt;/p&gt;
&lt;p&gt;## Patches
This bug has been fixed in the following containerd versions:&lt;/p&gt;
&lt;p&gt;* 2.3.2
* 2.2.5
* 2.1.9&lt;/p&gt;
&lt;p&gt;Users should update to these versions to resolve the issue.
## Workarounds
Users should only allow trusted images to be pulled.&lt;/p&gt;
&lt;p&gt;## 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](https://github.com/containerd/project/blob/main/SECURITY.md).&lt;/p&gt;
&lt;p&gt;## For more information
If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* Open an issue in [containerd](https://github.com…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-cvxm-645q-p574</guid>
    </item>
  </channel>
</rss>
