{"id":"CVE-2026-55074","aliases":["EUVD-2026-83940","GHSA-cxgv-hp74-jj7r","PYSEC-2026-3658"],"status":"published","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer'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'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's destination before the transfer runs. This issue has been fixed in version 2.0.0.","severity":{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00441,"percentile":0.38678,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-59"],"published":"2026-08-12T23:21:06Z","modified":"2026-10-28T02:30:58Z","fixes":[{"ecosystem":"PyPI","package":"ansible-jailexec","fixed_in":["2.0.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"ansible-jailexec","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}]},{"source":"osv","ecosystem":"PyPI","package":"ansible-jailexec","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}],"versions":["1.2.0","1.3.0"]},{"source":"osv","ecosystem":"PyPI","package":"ansible-jailexec","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}],"versions":["1.2.0","1.3.0"]}],"products":[{"vendor":"chofstede","product":"ansible_jailexec"}],"references":[{"url":"https://github.com/chofstede/ansible_jailexec/security/advisories/GHSA-cxgv-hp74-jj7r","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/chofstede/ansible_jailexec/pull/6","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/chofstede/ansible_jailexec/commit/6e80eecb2db7aebd1258fded6ae5c3aba1dd4123","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/chofstede/ansible_jailexec/blob/main/docs/security/advisory-2.0.0-jail-escape.md","tags":["x_refsource_MISC","advisory"]},{"url":"https://github.com/chofstede/ansible_jailexec/releases/tag/v2.0.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/advisories/GHSA-cxgv-hp74-jj7r","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55074.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55074","tags":["advisory"]},{"url":"https://github.com/chofstede/ansible_jailexec","tags":["package"]},{"url":"https://pypi.org/project/ansible-jailexec","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-55074","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer'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'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's destination before the transfer runs. This issue has been fixed in version 2.0.0.","status":"published","published":"2026-09-21T14:24:55.995Z","modified":"2026-09-21T15:44:36.603Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna"}],"cwes":["CWE-59"],"updated_at":"2026-11-02T14:20:11.925815Z"}],"euvd":[{"id":"EUVD-2026-83940","description":"Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer'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'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's destination before the transfer runs. This issue has been fixed in version 2.0.0.","status":"published","published":"2026-09-21T14:24:55Z","modified":"2026-09-21T15:44:36Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T17:28:05.36994Z"}],"ghsa":[{"id":"GHSA-cxgv-hp74-jj7r","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer's destination to a path on the jail host (\u003cjail filesystem root\u003e + \u003cdestination\u003e) 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.\n\nA party controlling content inside a managed jail (the jail'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).\n\nPreconditions: 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's destination before the transfer runs.\n\nPatches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p \u003cdir\u003e \u0026\u0026 cat \u003e \u003cdest\u003e for put_file; cat \u003c \u003csrc\u003e for fetch_file), so every path resolves within the jail's chroot. An in-jail symlink can at most redirect within the same jail and can no longer reach the host.\n\nWorkarounds: None in affected versions; upgrade to 2.0.0.","status":"published","published":"2026-08-12T23:21:06Z","modified":"2026-08-13T15:58:54Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-59"],"updated_at":"2026-11-02T14:41:00.097339Z"}],"nvd":[{"id":"CVE-2026-55074","description":"Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer'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'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's destination before the transfer runs. This issue has been fixed in version 2.0.0.","status":"published","published":"2026-09-21T15:17:29.627Z","modified":"2026-09-24T21:25:27.05Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"}],"cwes":["CWE-59"],"updated_at":"2026-11-02T14:12:50.043898Z"}],"osv":[{"id":"CVE-2026-55074","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Ansible FreeBSD Jail Connection Plugin is an Ansible connection plugin for FreeBSD Jails via jexec. Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer'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'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's destination before the transfer runs. This issue has been fixed in version 2.0.0.","status":"published","published":"2026-09-21T14:24:55.995Z","modified":"2026-10-28T02:30:58.840338684Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-59"],"updated_at":"2026-11-02T15:45:11.22012Z"},{"id":"GHSA-cxgv-hp74-jj7r","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer's destination to a path on the jail host (\u003cjail filesystem root\u003e + \u003cdestination\u003e) 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.\n\nA party controlling content inside a managed jail (the jail'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).\n\nPreconditions: 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's destination before the transfer runs.\n\nPatches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p \u003cdir\u003e \u0026\u0026 cat \u003e \u003cdest\u003e for put_file; cat \u003c \u003csrc\u003e for fetch_file), so every path resolves within the jail's chroot. An in-jail symlink can at most redirect within the same jail and can no longer reach the host.\n\nWorkarounds: None in affected versions; upgrade to 2.0.0.","status":"published","published":"2026-08-12T23:21:06Z","modified":"2026-08-19T12:55:55.015626437Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-59"],"updated_at":"2026-11-02T15:46:45.639885Z"},{"id":"PYSEC-2026-3658","title":"Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)","description":"Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer's destination to a path on the jail host (\u003cjail filesystem root\u003e + \u003cdestination\u003e) 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.\n\nA party controlling content inside a managed jail (the jail'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).\n\nPreconditions: 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's destination before the transfer runs.\n\nPatches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p \u003cdir\u003e \u0026\u0026 cat \u003e \u003cdest\u003e for put_file; cat \u003c \u003csrc\u003e for fetch_file), so every path resolves within the jail's chroot. An in-jail symlink can at most redirect within the same jail and can no longer reach the host.\n\nWorkarounds: None in affected versions; upgrade to 2.0.0.","status":"published","published":"2026-08-19T11:56:26.241512Z","modified":"2026-08-19T12:45:04.20816617Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T15:52:56.847083Z"}]}}