How severe is GHSA-cxgv-hp74-jj7r?

No CVSS score has been assigned to GHSA-cxgv-hp74-jj7r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cxgv-hp74-jj7r?

GHSA-cxgv-hp74-jj7r affects the following packages: ansible-jailexec (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cxgv-hp74-jj7r?

Update ansible-jailexec to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxgv-hp74-jj7r is resolved across your whole dependency graph.

How do I detect GHSA-cxgv-hp74-jj7r in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible-jailexec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cxgv-hp74-jj7r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-cxgv-hp74-jj7r actively exploited in the wild?

No public exploit code has been indexed for GHSA-cxgv-hp74-jj7r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cxgv-hp74-jj7r?

GHSA-cxgv-hp74-jj7r has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cxgv-hp74-jj7r?

GHSA-cxgv-hp74-jj7r is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cxgv-hp74-jj7r published, and has it been updated?

GHSA-cxgv-hp74-jj7r was published on August 12, 2026 and was last updated on August 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-cxgv-hp74-jj7r — ansible-jailexec

Fix: chofstede/ansible_jailexec@6e80eec

GHSA-cxgv-hp74-jj7r is a CWE-59 vulnerability in ansible-jailexec. A fix is available for ansible-jailexec — see the affected versions and patch details below.

Ansible FreeBSD Jail Connection Plugin: Jail escape via symlink following in put_file (host-side root mv)

Also known asCVE-2026-55074PYSEC-2026-3658

Published

Aug 12, 2026

Updated

Aug 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cxgv-hp74-jj7r.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍ansible-jailexec

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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: 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.

Patches: Fixed in 2.0.0. File transfers now run inside the jail via jexec (mkdir -p <dir> && cat > <dest> for put_file; cat < <src> 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.

Workarounds: None in affected versions; upgrade to 2.0.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ansible-jailexec`	all versions	2.0.0`pip install --upgrade 'ansible-jailexec==2.0.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible-jailexec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ansible-jailexec to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxgv-hp74-jj7r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Through version 1.3.0, the jailexec connection plugin's put_file resolved a transfer's destination to a path on the jail host (<jail filesystem root> + <destination>) 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 o

O3 Security · Impact-Aware SCA

Is GHSA-cxgv-hp74-jj7r in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works