Skip to main content
← All vulnerabilities
CVE-2026-46439PYSEC-2026-2425GHSA-GG2G-P7XC-QQMM

compliance-trestle Vulnerable to Remote Code Execution via Recursive Server-Side Template Injection (SSTI)

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 3.12.2, 4.0.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: total

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • oscal-compass compliance-trestle

    fixed in 3.12.2; From 4.0.0 · fixed in 4.0.3

  • compliance-trestlePyPI

    fixed in 3.12.2; From 4.0.0 · fixed in 4.0.3

  • compliance-trestlePyPI

    fixed in 3.12.2

  • compliance-trestlePyPI

    From 4.0.0 · fixed in 4.0.3

References 4

GitHub · oscal-compass/compliance-trestle

GitHub · pypa/advisory-database