Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, Trestle is vulnerable to server-side template injection that can lead to remote code execution. This occurs because the MDCleanInclude and MDSectionInclude Jinja2 tags re-parse untrusted Markdown content as template source code using a non-sandboxed jinja2.Environment. An attacker who controls content that Trestle renders, such as a crafted workspace Markdown file, a third-party SSP document, or a YAML lookup-table value, can inject a Jinja2 expression that traverses Python object internals to execute arbitrary operating system commands in the context of the Trestle process. This issue is fixed in versions 3.12.4 and 4.1.0.
CVE-2026-54757
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. 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
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
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%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026Server-Side Template Injection (SSTI) — Recursive Template Re-evaluation of Untrusted Data · Advisory · oscal-compass/compliance-trestle · GitHub
https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-jw39-3688-r4rxcommit 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/0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10Vendor Advisories for CVE-2026-54757(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 | Fixed in | Dependents |
|---|---|---|---|
| compliance-trestle | 0.0.2 ... 3.9.3 (99 versions) | 3.12.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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-08-30 01:54 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 02:30 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 15:18 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 15:56 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:34 UTCEG score recompute
- 2026-08-25 23:30 UTCEG score recompute
- 2026-08-25 23:15 UTCEG score recompute
- 2026-08-25 23:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2006-1318EG 9.3EPSS p97HIGH
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1308EG 9.3EPSS p95HIGH
- CVE-2006-1309EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p96HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
Frequently asked(5)
What is CVE-2026-54757?
When was CVE-2026-54757 disclosed?
Is CVE-2026-54757 actively exploited?
What is the CVSS score of CVE-2026-54757?
How do I remediate CVE-2026-54757?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54757
Is Your Infrastructure Affected by CVE-2026-54757?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.