<?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/tags/kata-containers/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 30 Apr 2026 20:57:17 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/kata-containers/feed.xml" rel="self" type="application/rss+xml"/><item><title>Contrast CLI CopyFile Policy Subversion via Symlinks Allows Guest Root Filesystem Writes</title><link>https://feed.craftedsignal.io/briefs/2026-04-contrast-copyfile-vuln/</link><pubDate>Thu, 30 Apr 2026 20:57:17 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-contrast-copyfile-vuln/</guid><description>A vulnerability in the CopyFile verification of Kata agent policies generated by the Contrast CLI allows arbitrary writes to the guest root filesystem, potentially leading to a full guest takeover.</description><content:encoded><![CDATA[<p>A vulnerability exists in the Kata agent policies generated by the Contrast CLI (versions prior to v1.19.1). Specifically, the <code>CopyFile</code> verification process is flawed, enabling a malicious host process to write arbitrary data to the guest root filesystem. This attack vector leverages the Kata agent&rsquo;s VSOCK interface, allowing a compromised host to connect to the agent and issue malicious <code>CopyFile</code> requests. The successful exploitation can overwrite critical security files or deceive the workload into divulging sensitive data. This flaw has a high impact, potentially resulting in a complete guest takeover. The issue was patched in Contrast v1.19.1.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>A malicious process gains the capability to connect to the Kata agent VSOCK.</li>
<li>The malicious process connects to the Kata agent via VSOCK.</li>
<li>The attacker crafts a series of <code>CopyFile</code> requests.</li>
<li>These <code>CopyFile</code> requests are designed to exploit the vulnerability in the Contrast CLI-generated Kata agent policies.</li>
<li>The attacker uses the <code>CopyFile</code> requests to create symlinks pointing to sensitive or critical system files.</li>
<li>The attacker then uses <code>CopyFile</code> requests to write arbitrary data to the targeted files via the created symlinks.</li>
<li>Security-critical files within the guest root filesystem are overwritten or modified by the attacker.</li>
<li>The compromised system facilitates a full guest takeover, potentially enabling further malicious activities within the containerized environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows a malicious host process to gain full control over the guest container. This can lead to data exfiltration, denial of service, or further lateral movement within the infrastructure. While the exact number of affected systems is not specified, any environment relying on affected Contrast CLI versions to generate Kata agent policies is potentially at risk. The impact is a full guest takeover.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Contrast CLI to version v1.19.1 or later to remediate the vulnerability.</li>
<li>If upgrading is not immediately possible, implement the policy-only fix described in the provided resources, specifically the rego fix, and pass it to <code>contrast generate --policy</code>.</li>
<li>Monitor network connections to the Kata agent VSOCK for unusual or unauthorized activity, especially originating from untrusted processes.</li>
<li>Implement host-based intrusion detection systems (HIDS) to detect unauthorized file modifications within the guest root filesystem.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>kata-containers</category><category>container-security</category><category>privilege-escalation</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>