Code Injection in compliance-trestle (CVE-2026-57170)
Summary
Code injection in compliance-trestle (CVE-2026-57170). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.1.0 or later.
Original description
The description as published by the source.
Reporter: Cavan Loughran, Celvex Group Inc.
Summary
The fix for CVE-2026-46439 (3.12.2 / 4.0.3) removed the recursive re-render loop in trestle/core/commands/author/jinja.py render_template, but the custom include tags in trestle/core/jinja/tags.py (MDSectionInclude, MDCleanInclude) still re-parse the CONTENT of an included markdown file as a Jinja2 template via Parser(self.environment, ).parse() in a plain (non-sandboxed) jinja2.Environment. Because the trestle markdown writers (ssp_io.py SSPMarkdownWriter, docs_control_writer.py DocsControlWriter) write OSCAL prose / component-description fields verbatim (the {{ -> [[ neutralization is applied to parameter tables only), attacker-controlled OSCAL data that flows into an included markdown file is interpreted as template code and can achieve arbitrary code execution on the runner. This is the same trust boundary and impact as CVE-2026-46439 via a sink the fix did not cover.
Affected versions
4.0.3 and earlier on this code path (the include tags predate and were untouched by the parent fix); the 3.12.x line likewise. Verified present in the fixed release 4.0.3 by direct source read.
Technical detail
Sink (UNCHANGED by the parent fix), trestle/core/jinja/tags.py:
MDSectionInclude.parse (the {% mdsection_include 'file.md' '# Section' %} tag), approximately:
md_content, _, _ = self.environment.loader.get_source(self.environment, markdown_source.value) # ~line 90
...
local_pars…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-57170 has been found in compliance-trestle.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade compliance-trestle to 4.1.0 or later.
If unsure, ask your IT team or search "compliance-trestle CVE-2026-57170" on the vendor's site.
CVE-2026-57170 (compliance-trestle) — CWE-94 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: 4.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in compliance-trestle.
Check the vendor advisory for the affected versions of compliance-trestle.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 4.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'compliance-trestle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'compliance-trestle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
compliance-trestleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade compliance-trestle to 4.1.0ステージング環境で 4.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com