Quick answers
- Is CVE-2026-45725 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45725 being exploited in the wild.
- How severe is CVE-2026-45725?
- High severity, with a CVSS score of 4, published 13 August 2026.
- Which products and versions are affected?
- compliance-trestle (PyPI) ECOSYSTEM:introduced=0,fixed=3.12.2,introduced=4.0.0,fixed=4.0.3, ECOSYSTEM:introduced=4.0.0,fixed=4.0.3.
- Is there a fix for CVE-2026-45725?
- Yes. compliance-trestle (PyPI): upgrade to 4.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45725 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45725?
- Check whether you run compliance-trestle (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- compliance-trestle (PyPI): upgrade to 4.0.3 or later
pip install "compliance-trestle>=4.0.3"
Technical details
A path traversal vulnerability exists in the HTTPSFetcher and SFTPFetcher components of compliance-trestle (specifically in trestle/core/remote/cache.py). The library constructs local cache file paths using unsanitized components from remote URLs, preserving '../' sequences. An attacker can provide a malicious OSCAL profile referencing a URL with traversal sequences, causing the fetched content to be written outside the intended cache directory. This can be leveraged for arbitrary file write and subsequent Remote Code Execution (RCE) by overwriting sensitive files like cron jobs, SSH authorized_keys, or Python modules. The issue is fixed in versions 4.0.3 and 3.12.2.
Affected products
- IBM compliance-trestle >= 4.0.0, <= 4.0.2
Identifiers
- CVE-2026-45725
- GHSA-g3vg-vx23-3858
- PYSEC-2026-2424
Timeline
- 2026-04-30: disclosed: Vulnerability identified in version 4.0.2
- 2026-05-27: advisory: GitHub Advisory GHSA-g3vg-vx23-3858 published
- 2026-05-27: patched: Fixed in versions 4.0.3 and 3.12.2