Trestle is vulnerable to arbitrary file write via path traversal in author generate commands (Incomplete fix of CVE-2026-46345)
Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, the catalog-generate, profile-generate, and ssp-generate author commands write generated Markdown to an attacker-influenced output path without path-traversal validation, allowing arbitrary file write outside the Trestle workspace. These commands join the user-supplied output argument onto the Trestle root and write to the result, but guard it only with an is_directory_name_allowed() task-name-collision check rather than the PathSecurityValidator.validate_local_path() guard used by the jinja command, so an absolute path or one containing traversal sequences escapes the workspace and writes files under an attacker-chosen location as the invoking process owner. The security boundary is crossed when a trusted CI job, shared service, or wrapper derives the output argument from repository-controlled, tenant-controlled, or otherwise untrusted data while expecting output to stay inside the workspace. When --force-overwrite is used, the selected output directory is first recursively deleted, extending the primitive to destruction of an attacker-chosen directory tree and enabling indirect code execution by overwriting files a pipeline later runs. This issue is fixed in versions 3.12.4 and 4.1.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-57171
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:18 UTC · Revision 1
Source evidence
Trestle is vulnerable to arbitrary file write via path traversal in author generate commands (Incomplete fix of CVE-2026-46345)
core-osv · Original sourcePublished 25 Aug 2026, 23:39 UTC
Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, the catalog-generate, profile-generate, and ssp-generate author commands write generated Markdown to an attacker-influenced output path without path-traversal validation, allowing arbitrary file write outside the Trestle workspace. These commands join the user-supplied output argument onto the Trestle root and write to the result, but guard it only with an is_directory_name_allowed() task-name-collision check rather than the PathSecurityValidator.validate_local_path() guard used by the jinja command, so an absolute path or one containing traversal sequences escapes the workspace and writes files under an attacker-chosen location as the invoking process owner. The security boundary is crossed when a trusted CI job, shared service, or wrapper derives the output argument from repository-controlled, tenant-controlled, or otherwise untrusted data while expecting output to stay inside the workspace. When --force-overwrite is used, the selected output directory is first recursively deleted, extending the primitive to destruction of an attacker-chosen directory tree and enabling indirect code execution by overwriting files a pipeline later runs. This issue is fixed in versions 3.12.4 and 4.1.0.
osv:CVE-2026-57171
Complete source record
{
"id": "92faf1c4b63553b7a561bca8a589600877a0a5bade2d9ea55f5c6c1cc67a26b4",
"url": "https://osv.dev/vulnerability/CVE-2026-57171",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Trestle is vulnerable to arbitrary file write via path traversal in author generate commands (Incomplete fix of CVE-2026-46345)",
"summary": "Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, the catalog-generate, profile-generate, and ssp-generate author commands write generated Markdown to an attacker-influenced output path without path-traversal validation, allowing arbitrary file write outside the Trestle workspace. These commands join the user-supplied output argument onto the Trestle root and write to the result, but guard it only with an is_directory_name_allowed() task-name-collision check rather than the PathSecurityValidator.validate_local_path() guard used by the jinja command, so an absolute path or one containing traversal sequences escapes the workspace and writes files under an attacker-chosen location as the invoking process owner. The security boundary is crossed when a trusted CI job, shared service, or wrapper derives the output argument from repository-controlled, tenant-controlled, or otherwise untrusted data while expecting output to stay inside the workspace. When --force-overwrite is used, the selected output directory is first recursively deleted, extending the primitive to destruction of an attacker-chosen directory tree and enabling indirect code execution by overwriting files a pipeline later runs. This issue is fixed in versions 3.12.4 and 4.1.0.",
"evidence": "osv:CVE-2026-57171",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-57171",
"aliases": [
"CVE-2026-57171",
"GHSA-r4vp-3vw6-r2x5",
"PYSEC-2026-4030"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/oscal-compass/compliance-trestle",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "5855179606e0d0f7656f7455b930ef12d32071e6"
},
{
"introduced": "d965ee5a9a1c2680c80bfa3e63cd75f4fc488881"
},
{
"fixed": "654bfaa0768aa6e4d495911e713c5f4e061e187e"
},
{
"fixed": "37ed44f5f2e074202c8eb7c2f203c05d19461cdc"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "3.12.4"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.1.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "37ed44f5f2e074202c8eb7c2f203c05d19461cdc"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "654bfaa0768aa6e4d495911e713c5f4e061e187e"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.1.0"
}
]
}
}
],
"versions": [
"v3.12.3",
"v4.0.3",
"v3.12.2",
"v3.12.1",
"v4.0.2",
"v3.12.0",
"v4.0.1",
"v4.0.0",
"v3.11.0",
"v3.10.4",
"v3.10.3",
"v3.10.2",
"v3.10.1",
"v3.10.0",
"v3.9.3",
"v3.9.2",
"v3.9.1",
"v3.9.0",
"v3.8.1",
"v3.8.0",
"v3.7.0",
"v3.6.0",
"v3.5.0",
"v3.4.0",
"v3.3.0",
"v3.2.0",
"v3.1.0",
"v3.0.1",
"v2.6.1",
"v2.6.0",
"v2.5.1",
"v2.5.0",
"v2.4.0",
"v2.3.1",
"v2.3.0",
"v2.2.1",
"v2.2.0",
"v2.1.1",
"v2.1.0",
"v2.0.0",
"v1.2.0",
"v1.1.0",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v0.37.0",
"v0.36.0",
"v0.35.0",
"v0.34.0",
"v0.33.0",
"v0.32.1",
"v0.32.0",
"v0.31.0",
"v0.30.0",
"v0.29.0",
"v0.28.1",
"v0.28.0",
"v0.27.2",
"v0.27.1",
"v0.27.0",
"v0.26.0",
"v0.25.1",
"v0.25.0",
"v0.24.0",
"v0.23.0",
"v0.22.1",
"v0.22.0",
"v0.21.0",
"v0.20.0",
"v0.19.0",
"v0.18.1",
"v0.18.0",
"v0.17.0",
"v0.16.0",
"v0.15.1",
"v0.15.0",
"v0.14.4",
"v0.14.3",
"v0.14.2",
"v0.14.1",
"v0.14.0",
"v0.13.1",
"v0.13.0",
"v0.12.0",
"v0.11.0",
"v0.10.0",
"v0.9.0",
"v0.8.1",
"v0.8.0",
"v0.7.2",
"v0.7.1",
"v0.7.0",
"v0.6.2",
"v0.6.1",
"v0.6.0",
"v0.4.0",
"v0.3.0",
"v0.2.2",
"v0.2.1",
"v0.2.0",
"v0.1.1",
"v0.1.0",
"v0.0.3",
"v0.0.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-57171.json"
}
}
],
"modified": "2026-10-28T02:30:37.853693285Z",
"provider": "osv",
"references": [
"https://github.com/oscal-compass/compliance-trestle/releases/tag/v4.1.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/57xxx/CVE-2026-57171.json",
"https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-4q5v-7g7x-j79w",
"https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-r4vp-3vw6-r2x5",
"https://nvd.nist.gov/vuln/detail/CVE-2026-57171",
"https://github.com/oscal-compass/compliance-trestle/commit/37ed44f5f2e074202c8eb7c2f203c05d19461cdc"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/57xxx/CVE-2026-57171.json"
}
},
"related_cves": [
{
"value": "CVE-2026-57171",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505260,
"published_at": "2026-08-25T23:39:16.186+00:00"
}