<?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>CVE-2026-44850 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-44850/</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>Thu, 14 May 2026 16:30:41 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-44850/feed.xml" rel="self" type="application/rss+xml"/><item><title>Portainer Bind Mount Restriction Bypass via HostConfig.Mounts (CVE-2026-44850)</title><link>https://feed.craftedsignal.io/briefs/2026-05-portainer-bind-mount-bypass/</link><pubDate>Thu, 14 May 2026 16:30:41 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-portainer-bind-mount-bypass/</guid><description>Portainer versions 2.33.0 through 2.33.7, 2.39.0 through 2.39.1, and 2.40.0 through 2.40.9 are vulnerable to CVE-2026-44850, a bind-mount restriction bypass via the `HostConfig.Mounts` array allowing regular users to mount host paths into containers and potentially compromise the host filesystem.</description><content:encoded><![CDATA[<p>Portainer, a container management platform, contains a vulnerability (CVE-2026-44850) where the &ldquo;Disable bind mounts for non-administrators&rdquo; security setting can be bypassed. This setting aims to prevent regular users from binding host paths into containers they create through the Portainer-mediated Docker API. However, the check only inspected the <code>HostConfig.Binds</code> array and not the equivalent <code>HostConfig.Mounts</code> array. An authenticated user with container-create rights on an environment where the restriction is enabled could exploit this vulnerability and mount any host path into their container by submitting a <code>bind</code>-typed entry under <code>HostConfig.Mounts</code>. This bypass can be exploited to gain unauthorized access to the Docker host&rsquo;s filesystem, compromising the entire system. Fixes were released in versions 2.33.8, 2.39.2, and 2.41.0.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker authenticates to Portainer as a regular user with container-create rights.</li>
<li>The targeted Portainer environment has the &ldquo;Disable bind mounts for non-administrators&rdquo; security setting enabled.</li>
<li>The attacker crafts a <code>POST /containers/create</code> request to the Docker API through the Portainer proxy.</li>
<li>In the request body, the attacker includes a <code>HostConfig.Mounts</code> array with a <code>bind</code>-typed entry. This entry specifies the host path to be mounted into the container.</li>
<li>The Portainer proxy, which only checks <code>HostConfig.Binds</code>, fails to detect the malicious bind mount configuration in <code>HostConfig.Mounts</code>.</li>
<li>The Docker daemon creates the container with the specified bind mount, granting the attacker&rsquo;s container access to the host filesystem.</li>
<li>The attacker executes commands within the container to read or write to the mounted host path, potentially accessing sensitive data or modifying system configurations.</li>
<li>The attacker compromises the host system, other containers, or achieves persistence by writing to authorized_keys or systemd units.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows a regular user to bypass bind mount restrictions and gain unauthorized access to the Docker host filesystem. This can lead to:</p>
<ul>
<li>Reading or writing any path on the Docker host filesystem, including sensitive files like <code>/etc/shadow</code> or SSH keys under <code>/root/.ssh</code>.</li>
<li>Compromising other containers on the same host by accessing their layers, volumes, and live state within <code>/var/lib/docker</code>.</li>
<li>Gaining full Docker API access by mounting <code>/var/run/docker.sock</code> into the container.</li>
<li>Writing persistence to the host by dropping SSH keys into <code>authorized_keys</code> or installing systemd units.</li>
</ul>
<p>This vulnerability affects installations where the bind-mount restriction was relied upon as the primary defense against host exposure, particularly in shared environments with non-administrator container creators.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Portainer to versions 2.33.8, 2.39.2, or 2.41.0 or later to patch CVE-2026-44850.</li>
<li>Deploy the Sigma rule <code>Detect Portainer HostConfig Mounts Bind Type (CVE-2026-44850)</code> to detect attempts to exploit this vulnerability by monitoring container creation events.</li>
<li>Audit recent container creations for <code>HostConfig.Mounts</code> of <code>Type: bind</code> from non-admin Portainer users as suggested in the advisory.</li>
<li>Revoke container-create rights from non-administrator accounts on affected environments until the patched release is deployed as described in the advisory.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>privilege-escalation</category><category>vulnerability</category><category>container</category><category>CVE-2026-44850</category></item></channel></rss>