CVE-2026-46345

compliance-trestle - jinja has an Arbitrary File Write via Path Traversal

An attacker can write files outside the intended workspace directory and overwrite sensitive files writable by the current user.

Possible impacts include:

• overwriting .github/workflows/*.yml to execute attacker-controlled GitHub Actions workflows
• overwriting .git/hooks/* for local code execution
• modifying user configuration files such as .bashrc
• tampering with repository files and generated compliance artifacts

In CI/CD environments, this may result in execution of attacker-controlled commands on build runners.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-46345 has a CVSS score of 8.4 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.3, 3.12.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-46345? CVE-2026-46345 is a high-severity path traversal vulnerability in compliance-trestle (pip), affecting versions >= 4.0.0, < 4.0.3. It is fixed in 4.0.3, 3.12.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-46345? CVE-2026-46345 has a CVSS score of 8.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of compliance-trestle are affected by CVE-2026-46345? compliance-trestle (pip) versions >= 4.0.0, < 4.0.3 is affected.
4. Is there a fix for CVE-2026-46345? Yes. CVE-2026-46345 is fixed in 4.0.3, 3.12.2. Upgrade to this version or later.
5. Is CVE-2026-46345 exploitable, and should I be worried? Whether CVE-2026-46345 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-46345 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-46345?
   • Upgrade compliance-trestle to 4.0.3 or later
   • Upgrade compliance-trestle to 3.12.2 or later