<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kata Containers - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/kata-containers/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sun, 09 Aug 2026 09:35:53 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/kata-containers/feed.xml" rel="self" type="application/rss+xml"/><item><title>Unauthorized mem-agent ttRPC methods in Kata Containers</title><link>https://feed.craftedsignal.io/briefs/2026-08-kata-mem-agent/</link><pubDate>Sun, 09 Aug 2026 09:35:53 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-kata-mem-agent/</guid><description>A vulnerability in the Kata Containers mem-agent component allows an untrusted host to invoke unauthorized ttRPC methods, resulting in potential memory tampering within confidential guest environments.</description><content:encoded><![CDATA[<p>The vulnerability, identified as CVE-2026-64676, resides within the Kata Containers mem-agent component. It involves an insufficient access control check within the ttRPC service, which is used for inter-process communication between the guest and the host or agent-related services. An untrusted host process or attacker with sufficient permissions on the host side can bypass security boundaries to interact with sensitive ttRPC methods. In the context of confidential computing, this flaw undermines the isolation guarantees of the confidential guest, as it provides a mechanism for unauthorized actors to read or modify the guest's memory space. Defenders should prioritize updating the Kata Containers runtime environment to versions where the mem-agent access control logic has been hardened.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for the tampering of confidential guest memory, effectively breaking the security boundary provided by confidential computing hardware and software stacks. This poses a significant risk to the integrity and confidentiality of workloads running in isolated environments.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Update the Kata Containers runtime to the latest security-hardened version provided by the upstream project. Review host-side access policies to ensure that only authorized processes have the ability to communicate with guest-side mem-agent sockets.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Kata Containers Guest-to-Host Root Escape via Virtiofs FUSE_SYMLINK</title><link>https://feed.craftedsignal.io/briefs/2026-05-kata-virtiofs-escape/</link><pubDate>Wed, 27 May 2026 22:51:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-kata-virtiofs-escape/</guid><description>A vulnerability in Kata Containers allows a guest root user to escalate privileges to host root by exploiting the virtiofs shared file system to create arbitrary symlinks on the host.</description><content:encoded><![CDATA[<p>A guest-to-host root escape vulnerability exists in Kata Containers when using the runtime-rs standalone virtio-fs path. This configuration, which runs <code>virtiofsd</code> on the host as root without sandboxing or seccomp, allows a malicious actor with root privileges inside the Kata guest VM to send raw FUSE requests directly to the host <code>virtiofsd</code>. Specifically, the <code>FUSE_SYMLINK</code> request can be leveraged to create arbitrary symlinks outside the intended virtio-fs shared directory. By creating symlinks in sensitive host paths like <code>/etc/cron.d</code>, an attacker can inject and execute arbitrary code as host root. This attack bypasses the guest kernel's normal filesystem validation and directly interacts with the host's file system management. The vulnerability affects Kata Containers versions prior to commit <code>2ffd1538a296cff93a357bfba0dfca747480a1f8</code>, and is reproducible using QEMU and Cloud Hypervisor.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains root-equivalent access inside the Kata guest VM.</li>
<li>Attacker identifies the virtio-fs PCI device within the guest using <code>/sys/devices/pci*</code>.</li>
<li>Attacker takes control of a virtio-fs queue in userspace, bypassing the guest kernel's virtio-fs client.</li>
<li>Attacker sends a <code>FUSE_INIT</code> request to initialize the FUSE connection.</li>
<li>Attacker discovers the runtime-rs sandbox ID and constructs the path to a guest-controlled payload, such as <code>/tmp/kata-go-escape-payload</code>, using the <code>passthrough</code> mount.</li>
<li>Attacker crafts a raw <code>FUSE_SYMLINK</code> request. The request specifies a new symlink name as an absolute path on the host, e.g., <code>/etc/cron.d/kata-go-escape-cron-&lt;pid&gt;</code>, and sets the symlink target to point to the guest-controlled payload through a <code>/proc/&lt;pid&gt;/root/...</code> path.</li>
<li>The host <code>virtiofsd</code> receives the <code>FUSE_SYMLINK</code> request and, due to the lack of proper validation, creates the symlink on the host filesystem in the specified location.</li>
<li>Host cron reads the <code>/etc/cron.d</code> directory, follows the newly created symlink, and executes the guest-controlled payload as host root.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation leads to complete compromise of the host system, as the attacker gains the ability to execute arbitrary commands as root. This allows the attacker to bypass the Kata Containers isolation and potentially access sensitive data, disrupt services, or further compromise the host infrastructure. The provided PoC demonstrated this vulnerability, confirming guest-root to host-root command execution by creating a proof file in the host's <code>/run</code> directory. This bypasses the container's isolation and impacts the entire host system.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to a patched version of Kata Containers that addresses CVE-2026-47243 to prevent exploitation.</li>
<li>Monitor process creation events on the host for the execution of unexpected binaries from <code>/etc/cron.d</code> using the provided Sigma rule <code>Detect Cron Job File Creation</code>.</li>
<li>Implement host-based intrusion detection systems (HIDS) to monitor for suspicious file system activity, particularly the creation of symlinks in sensitive directories such as <code>/etc/cron.d</code>.</li>
<li>Review and harden the configuration of <code>virtiofsd</code> to ensure proper validation of file paths and prevent the creation of symlinks outside the intended shared directory.</li>
<li>Enable and configure seccomp profiles to restrict the capabilities of the <code>virtiofsd</code> process, limiting its ability to perform actions that could lead to privilege escalation.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>kata-containers</category><category>virtiofs</category><category>fuse</category><category>privilege-escalation</category><category>container-escape</category></item><item><title>Kata Containers CopyFile Policy Subversion via Symlinks</title><link>https://feed.craftedsignal.io/briefs/2024-01-03-kata-containers-copyfile-symlink/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-03-kata-containers-copyfile-symlink/</guid><description>An oversight in the CopyFile policy in Kata Containers allows untrusted hosts to write to arbitrary locations inside the guest workload image via symlinks, enabling binary overwrites and data exfiltration.</description><content:encoded><![CDATA[<p>An oversight in the CopyFile policy within Kata Containers allows a malicious host to manipulate guest workload images. The vulnerability stems from insufficient validation within the <code>CopyFileRequest</code> policy, specifically related to symlink creation. The policy primarily checks the destination path of copied files but fails to adequately validate the target of symlinks created via the same API. This flaw was discovered by @calonso-nv and impacts environments where the <code>genpolicy</code> implementation is used to prevent host access to container images, including Confidential Containers workloads which rely on strong isolation. If the guest image is not protected from the host (e.g., when using unprotected host pull), the system is not vulnerable. The affected package is <code>go/github.com/kata-containers/kata-containers</code> versions prior to <code>0.0.0-20260422180503-1b9e49eb2763</code>.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a target file within the guest container image, such as a binary or configuration file they wish to overwrite.</li>
<li>The attacker crafts a <code>CopyFileRequest</code> to create a symbolic link within the <code>/run/kata-containers/shared/containers</code> directory.</li>
<li>The <code>path</code> parameter of the request specifies the location of the symlink within the shared directory.</li>
<li>The <code>data</code> parameter of the request specifies the target of the symbolic link, which points to the target file identified in step 1, inside the guest file system.</li>
<li>The Kata Agent processes the <code>CopyFileRequest</code>, creating the symbolic link within the shared directory, pointing to the target file inside the container image.</li>
<li>The attacker crafts a second <code>CopyFileRequest</code> to copy malicious data into the symlink created in step 5.</li>
<li>The Kata Agent writes the malicious data to the symlink, which then overwrites the original target file within the container image.</li>
<li>The attacker restarts the container or waits for the compromised binary to be executed, achieving arbitrary code execution within the guest.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to overwrite arbitrary files within container images managed by Kata Containers. This can lead to arbitrary code execution within the guest environment, data exfiltration, and privilege escalation. This is particularly critical in Confidential Containers environments where the trust model explicitly forbids host access to container images. Affected systems are those employing the upstream <code>genpolicy</code> implementation.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the patch or upgrade to <code>go/github.com/kata-containers/kata-containers</code> version <code>0.0.0-20260422180503-1b9e49eb2763</code> or later to address CVE-2026-41326.</li>
<li>Monitor the creation of symbolic links within the <code>/run/kata-containers/shared/containers</code> directory, using the provided Sigma rule, as this is an unusual operation (file_event).</li>
<li>Implement strict access controls and monitoring for the Kata Agent to prevent unauthorized <code>CopyFileRequest</code> messages.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>kata-containers</category><category>container-escape</category><category>symlink</category></item></channel></rss>