Trestle SSTI in Jinja2 include tags allows arbitrary code execution (Incomplete fix of CVE-2026-46439)
Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions prior to 3.12.4 and 4.0.0 through 4.0.3, the custom Jinja2 include tags mdsection_include and md_clean_include re-parse the content of an included Markdown file as Jinja2 template code in a non-sandboxed environment, allowing server-side template injection that can lead to arbitrary code execution. The MDSectionInclude and MDCleanInclude tags in Trestle/core/jinja/tags.py pass included file content to Parser(self.environment, ...).parse(), splicing it into the host template's compilation, and the environment is a plain jinja2.Environment rather than a SandboxedEnvironment, so any expressions in the file are evaluated with full access to the usual SSTI gadget chain. Because Trestle's Markdown writers emit OSCAL prose and component-description fields verbatim, applying delimiter neutralization only to parameter tables, attacker-controlled OSCAL data such as a control statement, part prose, or component description containing Jinja2 syntax flows into an included Markdown file and is executed when the include tag re-parses it. This issue is fixed in version 4.1.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-57170
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 06:02 UTC · Revision 1
Source evidence
Trestle SSTI in Jinja2 include tags allows arbitrary code execution (Incomplete fix of CVE-2026-46439)
core-osv · Original sourcePublished 25 Aug 2026, 23:18 UTC
Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions prior to 3.12.4 and 4.0.0 through 4.0.3, the custom Jinja2 include tags mdsection_include and md_clean_include re-parse the content of an included Markdown file as Jinja2 template code in a non-sandboxed environment, allowing server-side template injection that can lead to arbitrary code execution. The MDSectionInclude and MDCleanInclude tags in Trestle/core/jinja/tags.py pass included file content to Parser(self.environment, ...).parse(), splicing it into the host template's compilation, and the environment is a plain jinja2.Environment rather than a SandboxedEnvironment, so any expressions in the file are evaluated with full access to the usual SSTI gadget chain. Because Trestle's Markdown writers emit OSCAL prose and component-description fields verbatim, applying delimiter neutralization only to parameter tables, attacker-controlled OSCAL data such as a control statement, part prose, or component description containing Jinja2 syntax flows into an included Markdown file and is executed when the include tag re-parses it. This issue is fixed in version 4.1.0.
osv:CVE-2026-57170
Complete source record
{
"id": "ec1029f59e6eecfec95a503438bee889226227df7f35ee4e8781c13bb5115b09",
"url": "https://osv.dev/vulnerability/CVE-2026-57170",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Trestle SSTI in Jinja2 include tags allows arbitrary code execution (Incomplete fix of CVE-2026-46439)",
"summary": "Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions prior to 3.12.4 and 4.0.0 through 4.0.3, the custom Jinja2 include tags mdsection_include and md_clean_include re-parse the content of an included Markdown file as Jinja2 template code in a non-sandboxed environment, allowing server-side template injection that can lead to arbitrary code execution. The MDSectionInclude and MDCleanInclude tags in Trestle/core/jinja/tags.py pass included file content to Parser(self.environment, ...).parse(), splicing it into the host template's compilation, and the environment is a plain jinja2.Environment rather than a SandboxedEnvironment, so any expressions in the file are evaluated with full access to the usual SSTI gadget chain. Because Trestle's Markdown writers emit OSCAL prose and component-description fields verbatim, applying delimiter neutralization only to parameter tables, attacker-controlled OSCAL data such as a control statement, part prose, or component description containing Jinja2 syntax flows into an included Markdown file and is executed when the include tag re-parses it. This issue is fixed in version 4.1.0.",
"evidence": "osv:CVE-2026-57170",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-57170",
"aliases": [
"CVE-2026-57170",
"GHSA-mr95-65j8-9mxp",
"PYSEC-2026-4029"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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": "0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10"
},
{
"fixed": "5335ff873a2a68eb7de43df029bea09cadff22fd"
}
],
"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": "0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "5335ff873a2a68eb7de43df029bea09cadff22fd"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"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-57170.json"
}
}
],
"modified": "2026-10-28T02:30:42.909219732Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/57xxx/CVE-2026-57170.json",
"https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-mr95-65j8-9mxp",
"https://nvd.nist.gov/vuln/detail/CVE-2026-57170",
"https://github.com/oscal-compass/compliance-trestle/commit/0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10",
"https://github.com/oscal-compass/compliance-trestle/commit/5335ff873a2a68eb7de43df029bea09cadff22fd"
],
"provider_metadata": {
"cwe_ids": [
"CWE-1336",
"CWE-94"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/57xxx/CVE-2026-57170.json"
}
},
"related_cves": [
{
"value": "CVE-2026-57170",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 510932,
"published_at": "2026-08-25T23:18:29.487+00:00"
}