Description
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.
Published: 2026-08-25
Score: 7.7 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Compliance‑Trestle, the Python SDK used to generate OSCAL documents, contains a path traversal flaw in its author commands (catalog‑generate, profile‑generate, and ssp‑generate). The commands append a user‑supplied output path onto the Trestle workspace without proper path‑validation, allowing an attacker to write or overwrite files outside the expected directory tree. When the --force‑overwrite flag is used the targeted directory is deleted before writing, enabling destruction of an attacker‑defined directory tree and indirect code execution by overwriting files that a subsequent pipeline step will run.

Affected Systems

The vulnerability exists in Trestle versions prior to 3.12.4 and in the 4.0.0 through 4.0.3 releases. The affected product is the OSCal‑Compass compliance‑Trestle tool, which is typically used in CI/CD pipelines, shared services, or wrapper scripts that may trust unverified input.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.7. No EPSS score is available, and the issue is not listed in CISA’s KEV catalog. An attacker who can influence the output argument—such as a malicious CI job or a wrapper that derives the path from repository or tenant data—can write to arbitrary files, potentially overwriting critical configuration or executable files. The abuse of --force‑overwrite enhances the danger by allowing deletion of entire directory trees, which can be leveraged for indirect code execution in later pipeline stages.

Generated by OpenCVE AI on August 26, 2026 at 01:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Trestle 3.12.4, 4.1.0, or later where the path‑validation issue is fixed.
  • Avoid using the output path argument in CI or wrapper scripts when it could be supplied by untrusted sources; restrict the --force‑overwrite flag or only enable it for fully controlled directories.
  • Ensure the process owner has the minimum necessary file system permissions on the Trestle workspace to prevent unauthorized writes.

Generated by OpenCVE AI on August 26, 2026 at 01:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Oscal-compass
Oscal-compass compliance-trestle
Vendors & Products Oscal-compass
Oscal-compass compliance-trestle

Wed, 26 Aug 2026 00:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Trestle is vulnerable to arbitrary file write via path traversal in author generate commands (Incomplete fix of CVE-2026-46345)
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 7.7, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}


Subscriptions

Oscal-compass Compliance-trestle
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-25T23:39:16.186Z

Reserved: 2026-06-24T01:47:55.285Z

Link: CVE-2026-57171

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T02:00:05Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')