CVE-2026-54757 json
Trestle has Server-Side Template Injection (SSTI) via Recursive Template Re-evaluation of Untrusted Data
published 2026-08-25 2 mo ago modified 2026-09-10 1 mo ago also GHSA-jw39-3688-r4rx , PYSEC-2026-3817 , EUVD-2026-66209
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi compliance-trestle 3.12.4, 4.1.0
- github.com/oscal-compass/compliance-trestle@0f82d19 commit
- github.com/oscal-compass/compliance-trestle@5335ff8 commit
- github.com/oscal-compass/compliance-trestle#2257 pull request
- github.com/oscal-compass/compliance-trestle/releases/tag/v3.12.4 release
- github.com/oscal-compass/compliance-trestle/releases/tag/v4.1.0 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-54757 updated cvss 7.8
compliance-trestle: Trestle: Remote Code Execution via Server-Side Template Injection
-
Red Hat File Integrity Operator compliance/openshift-compliance-content-rhel8 Red Hat Hardened Images scap-security-guide 0.1.81-2.hum1not affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-jw39-3688-r4rx referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | compliance-trestle | <3.12.4 >=4.0.0, <4.1.0 |
3.12.4 4.1.0 |
Affected products
- oscal-compass compliance-trestle
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/oscal-compass/compliance-trestle/commit/0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10
web
-
github.com
/oscal-compass/compliance-trestle/commit/5335ff873a2a68eb7de43df029bea09cadff22fd
web
-
github.com
/oscal-compass/compliance-trestle/pull/2257
web
-
github.com
/oscal-compass/compliance-trestle/security/advisories/GHSA-jw39-3688-r4rx
exploit, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-54757
advisory
-
github.com
/oscal-compass/compliance-trestle
package
-
github.com
/oscal-compass/compliance-trestle/releases/tag/v3.12.4
web
-
github.com
/oscal-compass/compliance-trestle/releases/tag/v4.1.0
web
-
pypi.org
/project/compliance-trestle
package
-
github.com
/advisories/GHSA-jw39-3688-r4rx
advisory
Sources
- CVE List CVE-2026-54757
- GitHub Advisory GHSA-jw39-3688-r4rx
- NVD CVE-2026-54757
- OSV PYSEC-2026-3817
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.