Quick answers
- Is CVE-2026-46345 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46345 being exploited in the wild.
- How severe is CVE-2026-46345?
- High severity, with a CVSS score of 8.4, published 17 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-46345?
- 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-46345 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-46345?
- 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 `trestle author jinja` command within `trestle/core/commands/author/jinja.py`. The `-o/--output` argument fails to properly validate user-supplied paths, including absolute paths and traversal sequences like `../` or `..\`. An attacker can exploit this to write files outside the intended workspace, potentially overwriting sensitive files such as GitHub Actions workflows (`.github/workflows/*.yml`), Git hooks, or shell configuration files (`.bashrc`). This can be achieved with local access and no authentication, running with the privileges of the user executing the command. The issue is fixed in versions 3.12.2 and 4.0.3.
Affected products
- oscal-compass compliance-trestle >= 4.0.0, < 4.0.3; <= 3.12.1
Identifiers
- CVE-2026-46345
- GHSA-4q5v-7g7x-j79w
- PYSEC-2026-2423
Timeline
- 2026-05-27: disclosed
- 2026-05-28: advisory