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.
CVE-2026-57170
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 13th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 25, 2026
Last Modified
September 9, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026commit 5335ff873a2a (oscal-compass/compliance-trestle)
Fix landed in oscal-compass/compliance-trestle commit 5335ff873a2a — awaiting tagged release
https://github.com/oscal-compass/compliance-trestle/commit/5335ff873a2a68eb7de43df029bea09cadff22fdcommit 0f82d19bd42f (oscal-compass/compliance-trestle)
Fix landed in oscal-compass/compliance-trestle commit 0f82d19bd42f — awaiting tagged release
https://github.com/oscal-compass/compliance-trestle/commit/0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10Incomplete fix of CVE-2026-46439: SSTI / RCE via mdsection_include / md_clean_include re-parse in a non-sandboxed Jinja environment · Advisory · oscal-compass/compliance-trestle · GitHub
https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-mr95-65j8-9mxpVendor Advisories for CVE-2026-57170(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| compliance-trestle | 0.0.2 ... 4.0.3 (103 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 53× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-10 10:00 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescore
- 2026-10-09 03:40 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescore
- 2026-10-08 02:15 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescore
- 2026-10-06 21:11 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescore
- 2026-10-05 20:30 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescore
- 2026-10-05 08:04 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 16:16 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 21:36 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 20:57 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 20:08 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 06:20 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 23:14 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 22:17 UTCEG score recompute
Show 56 moreShow fewer
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 21:30 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-24 22:12 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 19:56 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 19:04 UTCEG score recompute
- 2026-09-22 06:43 UTCEG score recompute
- 2026-09-21 06:04 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 17:03 UTCEG score recompute
- 2026-09-19 04:42 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 03:56 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:28 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 13:43 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 00:43 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 00:04 UTCEG score recompute
- 2026-09-11 23:22 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 10:17 UTCEG score recompute
- 2026-09-10 21:54 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 00:55 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 18:13 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 17:34 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 16:54 UTCEG score recompute
- 2026-09-04 16:11 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:40 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:56 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 00:51 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 12:31 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 23:28 UTCEG score recompute
- 2026-08-28 22:50 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 00:44 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 00:05 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 23:25 UTCEG score recompute
- 2026-08-25 23:24 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
8 shownPyPI:compliance-trestle
Same CWE
10 shownCWE-94 · CWE-1336
Frequently asked(5)
What is CVE-2026-57170?
When was CVE-2026-57170 disclosed?
Is CVE-2026-57170 actively exploited?
What is the CVSS score of CVE-2026-57170?
How do I remediate CVE-2026-57170?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57170
Is Your Infrastructure Affected by CVE-2026-57170?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.