CVE-2026-46439

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

compliance-trestle is a tooling platform for managing compliance as code. Versions prior to 3.12.2 and 4.0.3 have a Server-Side Template Injection (SSTI) vulnerability exists in the trestle author jinja command. The command recursively evaluates rendered templates, allowing an attacker to achieve arbitrary command execution with privileges of the running process by injecting malicious payloads into data fields (such as SSP documents or Lookup Tables). The vulnerability does not require attacker control of the template itself. Only attacker-controlled input data rendered into a trusted template is required. This distinction is critical: the template author may only intend to render plain text (e.g., Title: {{ ssp.metadata.title }}), but because of the recursive parsing, the data field itself becomes executable. The vulnerability is caused by recursive re-compilation and re-rendering of already-rendered output. Versions 3.12.3 and 4.0.3 patch the issue.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 28, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available. Sources: github, github_commit.
Web page

advisory-database/vulns/compliance-trestle/PYSEC-2026-2425.yaml at main · pypa/advisory-database · GitHub

https://github.com/pypa/advisory-database/tree/main/vulns/compliance-trestle/PYSEC-2026-2425.yaml
GitHub commit

commit 7d107b3ac53c (oscal-compass/compliance-trestle)

Fix landed in oscal-compass/compliance-trestle commit 7d107b3ac53c — awaiting tagged release

https://github.com/oscal-compass/compliance-trestle/commit/7d107b3ac53caca7bde97a6278b23cd739d94525
GitHub commit

commit 247fcce289f6 (oscal-compass/compliance-trestle)

Fix landed in oscal-compass/compliance-trestle commit 247fcce289f6 — awaiting tagged release

https://github.com/oscal-compass/compliance-trestle/commit/247fcce289f60103f3d8e28d8ec51a6986b94fb6
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via Recursive Server-Side Template Injection (SSTI) · Advisory · oscal-compass/compliance-trestle · GitHub

https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-gg2g-p7xc-qqmm

Vendor Advisories for CVE-2026-46439(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.2 (100 versions)
  • every version up to 3.12.2: fixed in 3.12.2
  • 4.0.0 up to 4.0.3: fixed in 4.0.3
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46439?
CVE-2026-46439 is a high-severity vulnerability; its CVE record was published on May 28, 2026. compliance-trestle is a tooling platform for managing compliance as code. Versions prior to 3.12.2 and 4.0.3 have a Server-Side Template Injection (SSTI) vulnerability exists in the trestle author jinja command. The command recursively evaluates rendered templates, allowing an attacker to achieve…
When was the CVE record for CVE-2026-46439 published?
The CVE record for CVE-2026-46439 was published on May 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-46439 actively exploited?
CVE-2026-46439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46439?
CVE-2026-46439 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-46439?
A fix for CVE-2026-46439 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46439 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-46439

Explore →

Is Your Infrastructure Affected by CVE-2026-46439?

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

Book a Demo →Browse All CVEs