<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T04:59:49.249693+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cve-2026-50195</id>
    <title>CVE-2026-50195 — containerd: CRI checkpoint import allows local image tag poisoning</title>
    <updated>2026-11-21T04:59:49.250777+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> containerd</p>
<p>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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-50195"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-8472-1</id>
    <title>USN-8472-1 — containerd-app vulnerabilities</title>
    <updated>2026-11-21T04:59:49.250823+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: containerd-app, Ubuntu:22.04:LTS: containerd-app, Ubuntu:24.04:LTS: containerd-app, Ubuntu:25.10: containerd-app, Ubuntu:26.04:LTS: containerd-app</p>
<p>It was discovered that containerd incorrectly handled HTTP/2 SETTINGS
frames. A remote attacker could possibly use this issue to cause containerd
to enter an infinite loop, resulting in a denial of service. (CVE-2026-33814)</p>
<p>Jakub Ciolek and Kyle Elliott discovered that containerd incorrectly
handled group parsing when creating containers from images. An attacker
could possibly use this issue to cause containerd to consume excessive
memory, resulting in a denial of service. (CVE-2026-47262)</p>
<p>Henry Beberman and Robert Prast discovered that containerd incorrectly
validated image references when importing container checkpoints. An
attacker could possibly use this issue to poison the local image cache and
execute arbitrary code in other pods. This issue only affected Ubuntu
22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 25.10 and Ubuntu 26.04 LTS.
(CVE-2026-50195)</p>
<p>Robert Prast discovered that containerd incorrectly propagated labels
from image configurations to containers. An attacker could possibly use
this issue to execute arbitrary code on the host. (CVE-2026-53488)</p>
<p>Yuming Zhang, Song Li, Sangwon Ryu, Henry Beberman, Robert Prast, Kyle
Elliott and Zhenchen Wang discovered that containerd incorrectly validated
symlinked paths when restoring container checkpoints. An attacker could
possibly use this issue to read arbitrary files on the host, resulting in
information disclosure. This issue only affected Ubuntu 22.04 LTS, Ubuntu
24.04 LTS, Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-5348…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-8472-1"/>
  </entry>
</feed>
