https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 20:14:42 +0000 https://vulnerability.circl.lu/vuln/cve-2026-55074 <p><strong>Affected:</strong> chofstede ansible_jailexec</p> <p>Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin&#39;s put_file resolved a transfer&#39;s destination to a path on the jail host ( + ) and ran mkdir -p and mv there as root on the host. Those commands follow symbolic links, and the path was operated on outside the jail, so a symlink existing inside the jail was followed by the host-side, root-privileged mv. A party controlling content inside a managed jail (the jail&#39;s root, or any process able to create a symlink in a directory an Ansible task later writes to) can therefore cause an arbitrary root-owned write on the host, outside the jail — a full jail escape. Arbitrary root-owned host writes are readily escalated to host compromise (e.g. cron, rc.d, authorized_keys). Preconditions for this vulnerability are that the operator runs a copy/template/fetch-style task (anything using put_file) against the jail, and the attacker can place a symlink inside the jail at or above the task&#39;s destination before the transfer runs. This issue has been fixed in version 2.0.0.</p> <p><strong>Affected:</strong> chofstede ansible_jailexec</p> <p>Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin&#39;s put_file resolved a transfer&#39;s destination to a path on the jail host ( + ) and ran mkdir -p and mv there as root on the host. Those commands follow symbolic links, and the path was operated on outside the jail, so a symlink existing inside the jail was followed by the host-side, root-privileged mv. A party controlling content inside a managed jail (the jail&#39;s root, or any process able to create a symlink in a directory an Ansible task later writes to) can therefore cause an arbitrary root-owned write on the host, outside the jail — a full jail escape. Arbitrary root-owned host writes are readily escalated to host compromise (e.g. cron, rc.d, authorized_keys). Preconditions for this vulnerability are that the operator runs a copy/template/fetch-style task (anything using put_file) against the jail, and the attacker can place a symlink inside the jail at or above the task&#39;s destination before the transfer runs. This issue has been fixed in version 2.0.0.</p> https://vulnerability.circl.lu/vuln/cve-2026-55074 https://vulnerability.circl.lu/vuln/ghsa-cxgv-hp74-jj7r <p><strong>Affected:</strong> PyPI: ansible-jailexec</p> <p>Through version 1.3.0, the jailexec connection plugin&#39;s put_file resolved a transfer&#39;s destination to a path on the jail host (&lt;jail filesystem root&gt; + &lt;destination&gt;) and ran mkdir -p and mv there as root on the host. Those commands follow symbolic links, and the path was operated on outside the jail, so a symlink existing inside the jail was followed by the host-side, root-privileged mv.</p> <p>A party controlling content inside a managed jail (the jail&#39;s root, or any process able to create a symlink in a directory an Ansible task later writes to) can therefore cause an arbitrary root-owned write on the host, outside the jail — a full jail escape. Arbitrary root-owned host writes are readily escalated to host compromise (e.g. cron, rc.d, authorized_keys).</p> <p>Preconditions: the operator runs a copy/template/fetch-style task (anything using put_file) against the jail, and the attacker can place a symlink inside the jail at or above the task&#39;s destination before the transfer runs.</p> <p>Patches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p &lt;dir&gt; &amp;&amp; cat &gt; &lt;dest&gt; for put_file; cat &lt; &lt;src&gt; for fetch_file), so every path resolves within the jail&#39;s chroot. An in-jail symlink can at most redirect within the same jail and can no longer reach the host.</p> <p>Workarounds: None in affected versions; upgrade to 2.0.0.</p> <p><strong>Affected:</strong> PyPI: ansible-jailexec</p> <p>Through version 1.3.0, the jailexec connection plugin&#39;s put_file resolved a transfer&#39;s destination to a path on the jail host (&lt;jail filesystem root&gt; + &lt;destination&gt;) and ran mkdir -p and mv there as root on the host. Those commands follow symbolic links, and the path was operated on outside the jail, so a symlink existing inside the jail was followed by the host-side, root-privileged mv.</p> <p>A party controlling content inside a managed jail (the jail&#39;s root, or any process able to create a symlink in a directory an Ansible task later writes to) can therefore cause an arbitrary root-owned write on the host, outside the jail — a full jail escape. Arbitrary root-owned host writes are readily escalated to host compromise (e.g. cron, rc.d, authorized_keys).</p> <p>Preconditions: the operator runs a copy/template/fetch-style task (anything using put_file) against the jail, and the attacker can place a symlink inside the jail at or above the task&#39;s destination before the transfer runs.</p> <p>Patches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p &lt;dir&gt; &amp;&amp; cat &gt; &lt;dest&gt; for put_file; cat &lt; &lt;src&gt; for fetch_file), so every path resolves within the jail&#39;s chroot. An in-jail symlink can at most redirect within the same jail and can no longer reach the host.</p> <p>Workarounds: None in affected versions; upgrade to 2.0.0.</p> https://vulnerability.circl.lu/vuln/ghsa-cxgv-hp74-jj7r