<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T18:46:07.378580+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/fkie_cve-2026-50540</id>
    <title>fkie_cve-2026-50540</title>
    <updated>2026-09-29T18:46:07.381536+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Prior to version 4.0.0, kata-runtime is vulnerable to host code execution via an unvalidated configuration path annotation. The runtime accepts an arbitrary io.katacontainers.config_path pod annotation and loads the referenced host TOML file without restriction. As a result, a pod user who can place a file at a host-visible path can supply a configuration that selects an attacker-controlled hypervisor or virtio-fs daemon binary, executing code as root on the host. This issue is fixed in version 4.0.0.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-50540"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/msrc_cve-2026-50540</id>
    <title>msrc_CVE-2026-50540 — Kata Containers: Config Path Annotation Arbitrary File Loading</title>
    <updated>2026-09-29T18:46:07.381616+00:00</updated>
    <content>msrc_CVE-2026-50540</content>
    <link href="https://vulnerability.circl.lu/vuln/msrc_cve-2026-50540"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/oesa-2026-3405</id>
    <title>OESA-2026-3405 — kata-containers security update</title>
    <updated>2026-09-29T18:46:07.381654+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP4: kata-containers, openEuler:20.03-LTS-SP4: kata-containers, openEuler:22.03-LTS-SP4: kata-containers, openEuler:24.03-LTS-SP1: kata-containers, openEuler:24.03-LTS-SP3: kata-containers</p>
<p>This is core component of Kata Container, to make it work, you need a isulad/docker engine.

Security Fix(es):</p>
<p>Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Prior to version 4.0.0, kata-runtime is vulnerable to host code execution via an unvalidated configuration path annotation. The runtime accepts an arbitrary io.katacontainers.config_path pod annotation and loads the referenced host TOML file without restriction. As a result, a pod user who can place a file at a host-visible path can supply a configuration that selects an attacker-controlled hypervisor or virtio-fs daemon binary, executing code as root on the host. This issue is fixed in version 4.0.0.(CVE-2026-50540)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/oesa-2026-3405"/>
  </entry>
</feed>
