CVE-2026-57170

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG 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 computed
Severity78% × 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, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 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/5335ff873a2a68eb7de43df029bea09cadff22fd
github_commit

commit 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/0f82d19bd42f9cc0f1b3acd7fc3f6dafe3b6ae10
githubMentions a patch (unverified)🟡 PoC Available

Incomplete 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-9mxp

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
compliance-trestle0.0.2 ... 4.0.3 (103 versions)
  • every version up to 3.12.4: fixed in 3.12.4
  • 4.0.0 up to 4.1.0: fixed in 4.1.0
—

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.

  1. 2026-10-10 10:00 UTCEG score recompute
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-09 03:40 UTCEG score recompute
  4. 2026-10-08 17:13 UTCEPSS rescore
  5. 2026-10-08 02:15 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-06 21:11 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-05 20:30 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-05 08:04 UTCEG score recompute
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-03 16:16 UTCEG score recompute
  14. 2026-10-03 14:26 UTCEPSS rescore
  15. 2026-10-02 21:36 UTCEG score recompute
  16. 2026-10-02 17:56 UTCEPSS rescore
  17. 2026-10-01 20:57 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-09-30 20:08 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescore
  21. 2026-09-30 06:20 UTCEG score recompute
  22. 2026-09-29 15:22 UTCEPSS rescore
  23. 2026-09-28 23:14 UTCEG score recompute
  24. 2026-09-28 13:51 UTCEPSS rescore
  25. 2026-09-27 22:17 UTCEG score recompute
Show 56 more
  1. 2026-09-27 13:48 UTCEPSS rescore
  2. 2026-09-26 21:30 UTCEG score recompute
  3. 2026-09-26 15:59 UTCEPSS rescore
  4. 2026-09-24 22:12 UTCEG score recompute
  5. 2026-09-24 14:04 UTCEPSS rescore
  6. 2026-09-23 19:56 UTCEG score recompute
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-22 19:04 UTCEG score recompute
  9. 2026-09-22 06:43 UTCEG score recompute
  10. 2026-09-21 06:04 UTCEG score recompute
  11. 2026-09-20 20:16 UTCEPSS rescore
  12. 2026-09-19 17:03 UTCEG score recompute
  13. 2026-09-19 04:42 UTCEG score recompute
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-18 03:56 UTCEG score recompute
  16. 2026-09-17 19:31 UTCEPSS rescore
  17. 2026-09-16 14:28 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 13:43 UTCEG score recompute
  21. 2026-09-15 03:11 UTCEPSS rescore
  22. 2026-09-14 00:43 UTCEG score recompute
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-13 00:04 UTCEG score recompute
  25. 2026-09-11 23:22 UTCEG score recompute
  26. 2026-09-11 14:53 UTCEPSS rescore
  27. 2026-09-11 10:17 UTCEG score recompute
  28. 2026-09-10 21:54 UTCEG score recompute
  29. 2026-09-10 09:35 UTCEPSS rescore
  30. 2026-09-09 00:55 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescore
  32. 2026-09-07 18:13 UTCEG score recompute
  33. 2026-09-07 16:01 UTCEPSS rescore
  34. 2026-09-06 17:34 UTCEG score recompute
  35. 2026-09-06 13:47 UTCEPSS rescore
  36. 2026-09-05 16:54 UTCEG score recompute
  37. 2026-09-04 16:11 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescore
  39. 2026-09-02 14:40 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescore
  41. 2026-09-01 13:56 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescore
  43. 2026-09-01 04:40 UTCEPSS rescore
  44. 2026-08-31 00:51 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescore
  46. 2026-08-30 12:31 UTCEG score recompute
  47. 2026-08-30 01:22 UTCEPSS rescore
  48. 2026-08-28 23:28 UTCEG score recompute
  49. 2026-08-28 22:50 UTCEG score recompute
  50. 2026-08-28 21:42 UTCEPSS rescore
  51. 2026-08-28 00:44 UTCEG score recompute
  52. 2026-08-27 14:25 UTCEPSS rescore
  53. 2026-08-27 00:05 UTCEG score recompute
  54. 2026-08-26 14:46 UTCEPSS rescore
  55. 2026-08-25 23:25 UTCEG score recompute
  56. 2026-08-25 23:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57170?
CVE-2026-57170 is a high vulnerability published on August 25, 2026. 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 mdsectioninclude and mdclean_include re-parse the content of an included Markdown file as Jinja2 template…
When was CVE-2026-57170 disclosed?
CVE-2026-57170 was first published on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57170 actively exploited?
CVE-2026-57170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57170?
CVE-2026-57170 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57170?
A fix for CVE-2026-57170 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57170 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57170

Explore →

Is Your Infrastructure Affected by CVE-2026-57170?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.