CVE-2024-56201

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: MODERATE) published 2024-12-23. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-3585 (ENISA EUVD) · GHSA-gmj6-6f8f-6699 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Jinja is an extensible templating engine. In versions on the 3.x branch prior to 3.1.5, a bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used. To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates where the template author can also choose the template filename. This vulnerability is fixed in 3.1.5.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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.

The score's inputs: 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

December 23, 2024

Last Modified

September 22, 2025

Advisory Details (4)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Sandbox breakout through malicious filenames · Advisory · pallets/jinja · GitHub

https://github.com/pallets/jinja/security/advisories/GHSA-gmj6-6f8f-6699
GitHub release Patch Available

Release 3.1.5 (pallets/jinja)

Patch available: pallets/jinja 3.1.5

https://github.com/pallets/jinja/releases/tag/3.1.5
Web page

f-string sytax error when importing macro in a template which filename is also a template · Issue #1792 · pallets/jinja · GitHub

https://github.com/pallets/jinja/issues/1792
GitHub commit Patch Available

commit 767b23617628 (pallets/jinja)

Patch available: pallets/jinja 3.1.5 (contains commit 767b23617628)

https://github.com/pallets/jinja/commit/767b23617628419ae3709ccfb02f9602ae9fe51f

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-jinja2-0:3.1.5-1.el8pc2025-04-01redhat
redhatrhoai/odh-model-registry-rhel8:v2.16.2-17424892332025-03-31redhat
redhatrhdh/rhdh-hub-rhel9:1.52025-03-27redhat
redhatopenshift4/sriov-network-metrics-exporter-rhel9:v4.18.0-202501230001.p0.g4098872.assembly.stream.el92025-02-25redhat
redhatopenstack-ansible-core-0:2.14.2-4.6.el9ost2025-02-25redhat
redhatquay/quay-rhel8:v3.9.10-72025-02-24redhat
redhatpython-jinja2-0:3.0.1-6.el9.22025-02-13redhat
redhatopenshift4/ose-ansible-rhel9-operator:v4.16.0-202501311735.p0.g2cb0020.assembly.stream.el92025-02-12redhat
redhatdiscovery/discovery-ui-rhel9:1.12.0-12025-02-10redhat
redhatquay/quay-rhel8:v3.10.8-62025-02-06redhat
redhatopenshift4/ose-ansible-rhel9-operator:v4.17.0-202501300634.p0.g9cb5839.assembly.stream.el92025-02-05redhat
redhatansible-automation-platform/ee-minimal-rhel9:2.15.13-102025-02-05redhat
redhatpython-jinja2-0:3.1.5-1.el92025-01-28redhat
redhatpython3.11-jinja2-0:3.1.5-1.el9ap2025-01-28redhat
redhatansible-automation-platform/ee-minimal-rhel9:2.18.1-42025-01-28redhat
redhatpython-jinja2-0:3.1.5-1.el9ap2025-01-27redhat
redhatansible-automation-platform-24/lightspeed-rhel8-operator:2.4-332025-01-27redhat
redhatrhdh-hub-container-1.3-1382025-01-22redhat
redhatquay/quay-rhel8:v3.13.3-62025-01-20redhat
redhatrhdh/rhdh-hub-rhel9:1.4-17370558462025-01-20redhat
redhatfence-agents-0:4.10.0-62.el9_4.102025-01-15redhat
redhatfence-agents-0:4.10.0-43.el9_2.112025-01-15redhat
redhatansible-automation-platform-25/lightspeed-rhel8:2.5.250107-12025-01-15redhat
redhatfence-agents-0:4.10.0-20.el9_0.202025-01-15redhat
redhatfence-agents-0:4.10.0-76.el9_5.42025-01-14redhat
pipjinja2 @ 3.1.5 (fixes >= 3.0.0, <= 3.1.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(11 across 11 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jinja23.1.2-1, 3.1.2-1+deb12u1
  • every version up to 3.1.2-1+deb12u2: fixed in 3.1.2-1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.5-1: fixed in 3.1.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.5-1: fixed in 3.1.5-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jinja23.0.0 ... 3.1.4 (9 versions)
  • 3.0.0 up to 3.1.5: fixed in 3.1.5
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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.

Showing the most recent 95 of 211 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-01 08:10 UTCGHSA enrichmentGHSA-gmj6-6f8f-6699 · GitHub severity MODERATE · GitHub CVSS 8.8
  3. 2026-11-01 08:10 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-27 18:45 UTCEG score recompute
  9. 2026-10-27 18:45 UTCVendor advisory
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-25 16:55 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-19 15:29 UTCEG score recompute
  21. 2026-10-19 15:29 UTCVendor advisory
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-18 05:59 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 70 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-12 17:37 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-11 21:03 UTCEG score recompute
  7. 2026-10-11 15:55 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-10 05:33 UTCOSV refresh
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-02 16:24 UTCEG score recompute
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-09-20 15:14 UTCOSV refresh
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-09-01 15:24 UTCOSV refresh
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  52. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-08-15 16:37 UTCOSV refresh
  62. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  66. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  67. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  68. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  69. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  70. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Frequently asked(5)

What is CVE-2024-56201?
CVE-2024-56201 is a high-severity vulnerability; its CVE record was published on December 23, 2024. Jinja is an extensible templating engine. In versions on the 3.x branch prior to 3.1.5, a bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used. To exploit the vulnerability,…
When was the CVE record for CVE-2024-56201 published?
The CVE record for CVE-2024-56201 was published on December 23, 2024. 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 22, 2025; the record at its source may have been updated since.
Is CVE-2024-56201 actively exploited?
CVE-2024-56201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56201?
CVE-2024-56201 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-56201?
A fix for CVE-2024-56201 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56201 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-2024-56201

Explore →

Is Your Infrastructure Affected by CVE-2024-56201?

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