Description
compliance-trestle is a tooling platform for managing compliance as code. Versions prior to 3.12.2 and 4.0.3 have a Server-Side Template Injection (SSTI) vulnerability exists in the `trestle author jinja` command. The command recursively evaluates rendered templates, allowing an attacker to achieve arbitrary command execution with privileges of the running process by injecting malicious payloads into data fields (such as SSP documents or Lookup Tables). The vulnerability does not require attacker control of the template itself. Only attacker-controlled input data rendered into a trusted template is required. This distinction is critical: the template author may only intend to render plain text (e.g., `Title: {{ ssp.metadata.title }}`), but because of the recursive parsing, the data field itself becomes executable. The vulnerability is caused by recursive re-compilation and re-rendering of already-rendered output. Versions 3.12.3 and 4.0.3 patch the issue.
Published: 2026-08-14
Score: 7.8 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a Server‑Side Template Injection in the `trestle author jinja` command, causing the tool to recursively recompile and render already rendered output. By injecting malicious Jinja payloads into data fields such as SSP documents or lookup tables, an attacker can cause the tool to execute arbitrary commands with the privileges of the running process. The vulnerable component does not require direct control of the template; only attacker‑controlled data rendered within a trusted template is sufficient.

Affected Systems

Affected versions are all releases of compliance‑trestle prior to 3.12.2 and 4.0.3. The patch is included in 3.12.3 and 4.0.3. The product is developed by oscal‑compass and used for compliance as code.

Risk and Exploitability

The CVSS score is 7.8. The EPSS score is unavailable, and the issue is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector is an attacker who can supply untrusted data to the trestle author jinja command, which may be local or remote depending on how the tool is invoked. Successful exploitation would give the attacker full control of the host where compliance‑trestle is running.

Generated by OpenCVE AI on August 14, 2026 at 17:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade compliance‑trestle to version 3.12.3 or later, or 4.0.3 or later.
  • If an upgrade is not possible, restrict access to the trestle author jinja command to trusted users and prevent untrusted data from being processed.
  • Implement input validation or escaping for all data fields rendered by the tool to prevent SSTI, such as removing or escaping Jinja template delimiters.

Generated by OpenCVE AI on August 14, 2026 at 17:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-gg2g-p7xc-qqmm compliance-trestle Vulnerable to Remote Code Execution via Recursive Server-Side Template Injection (SSTI)
History

Fri, 14 Aug 2026 17: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

Fri, 14 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Description compliance-trestle is a tooling platform for managing compliance as code. Versions prior to 3.12.2 and 4.0.3 have a Server-Side Template Injection (SSTI) vulnerability exists in the `trestle author jinja` command. The command recursively evaluates rendered templates, allowing an attacker to achieve arbitrary command execution with privileges of the running process by injecting malicious payloads into data fields (such as SSP documents or Lookup Tables). The vulnerability does not require attacker control of the template itself. Only attacker-controlled input data rendered into a trusted template is required. This distinction is critical: the template author may only intend to render plain text (e.g., `Title: {{ ssp.metadata.title }}`), but because of the recursive parsing, the data field itself becomes executable. The vulnerability is caused by recursive re-compilation and re-rendering of already-rendered output. Versions 3.12.3 and 4.0.3 patch the issue.
Title compliance-trestle Vulnerable to Remote Code Execution via Recursive Server-Side Template Injection (SSTI)
Weaknesses CWE-1336
CWE-94
References
Metrics cvssV3_1

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


Subscriptions

Oscal-compass Compliance-trestle
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-14T16:34:17.243Z

Reserved: 2026-05-13T22:18:22.830Z

Link: CVE-2026-46439

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-14T17:18:14.853

Modified: 2026-08-14T17:18:14.853

Link: CVE-2026-46439

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-14T18:00:12Z

Weaknesses
  • CWE-1336

    Improper Neutralization of Special Elements Used in a Template Engine

  • CWE-94

    Improper Control of Generation of Code ('Code Injection')