Description
compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the compliance-trestle library's profile import mechanism resolves `trestle://` URIs and relative file paths by joining them with `trestle_root` and calling `.resolve()`, but performs no boundary check to ensure the resolved path stays within the trestle workspace. An attacker can craft a malicious OSCAL profile YAML with `imports[].href` containing path traversal sequences to read arbitrary files from the server filesystem. Versions 3.12.3 and 4.0.3 patch the issue.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| oscal-compass | compliance-trestle | < 3.12.2, >= 4.0.0, < 4.0.3 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | compliance-trestle | >= 4.0.0, < 4.0.3 | 4.0.3 | GHSA-mj4x-vf5c-5xg8 |
| PyPI | compliance-trestle | < 3.12.2 | 3.12.2 | GHSA-mj4x-vf5c-5xg8 |
| PyPI | compliance-trestle | < 3.12.2 · >= 4.0.0, < 4.0.3 | 3.12.2, 4.0.3 | PYSEC-2026-2426 |
References
- https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-mj4x-vf5c-5xg8
- https://github.com/oscal-compass/compliance-trestle/commit/5c65c5926fe7ca908b9c1d281f904e7d97ba8310
- https://github.com/oscal-compass/compliance-trestle/commit/d00a0c2f702c24f7016009fbd626036f5c46f47b
- https://github.com/pypa/advisory-database/tree/main/vulns/compliance-trestle/PYSEC-2026-2426.yaml