CVE-2024-56201

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (21st 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, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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/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
Severity88% × 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.3%
EPSS %ILE
21st
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

December 23, 2024

Last Modified

September 22, 2025

Advisory Details (4)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github_release, github.
githubMentions 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
generic

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

Vendor Advisories for CVE-2024-56201(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jinja2 (2.10.1-2ubuntu0.4) @ focal2026-05-23ubuntu
ubuntupython3-jinja2 (2.8-1ubuntu0.1+esm5) @ xenial2026-05-23ubuntu
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
redhatopenstack-ansible-core-0:2.14.2-4.6.el9ost2025-02-25redhat
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
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
redhatansible-automation-platform/ee-minimal-rhel9:2.18.1-42025-01-28redhat
redhatpython3.11-jinja2-0:3.1.5-1.el9ap2025-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
redhatrhdh/rhdh-hub-rhel9:1.4-17370558462025-01-20redhat
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-62.el9_4.102025-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

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

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-10-10 05:33 UTCOSV refresh
  2. 2026-10-09 20:05 UTCEPSS rescore
  3. 2026-10-08 17:08 UTCEPSS rescore
  4. 2026-10-07 23:46 UTCEPSS rescore
  5. 2026-10-06 15:16 UTCEPSS rescore
  6. 2026-10-05 17:41 UTCEPSS rescore
  7. 2026-10-04 23:20 UTCEPSS rescore
  8. 2026-10-03 14:24 UTCEPSS rescore
  9. 2026-10-02 16:24 UTCEG score recompute
  10. 2026-10-01 19:48 UTCEPSS rescore
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-28 13:50 UTCEPSS rescore
  14. 2026-09-27 13:44 UTCEPSS rescore
  15. 2026-09-27 13:44 UTCEPSS rescore
  16. 2026-09-26 15:57 UTCEPSS rescore
  17. 2026-09-24 14:01 UTCEPSS rescore
  18. 2026-09-23 13:46 UTCEPSS rescore
  19. 2026-09-22 14:47 UTCEPSS rescore
  20. 2026-09-20 20:14 UTCEPSS rescore
  21. 2026-09-20 20:14 UTCEPSS rescore
  22. 2026-09-20 15:14 UTCOSV refresh
  23. 2026-09-18 19:26 UTCEPSS rescore
  24. 2026-09-16 14:06 UTCEPSS rescore
  25. 2026-09-16 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 05:12 UTCEPSS rescore
  2. 2026-09-15 03:08 UTCEPSS rescore
  3. 2026-09-13 16:45 UTCEPSS rescore
  4. 2026-09-12 14:59 UTCEPSS rescore
  5. 2026-09-11 14:51 UTCEPSS rescore
  6. 2026-09-11 09:35 UTCEPSS rescore
  7. 2026-09-10 09:33 UTCEPSS rescore
  8. 2026-09-08 21:59 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-04 13:59 UTCEPSS rescore
  12. 2026-09-04 05:05 UTCEPSS rescore
  13. 2026-09-02 14:10 UTCEPSS rescore
  14. 2026-09-01 15:24 UTCOSV refresh
  15. 2026-09-01 13:52 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:44 UTCEPSS rescore
  22. 2026-08-25 13:47 UTCEPSS rescore
  23. 2026-08-24 14:15 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:47 UTCEPSS rescore
  26. 2026-08-20 22:54 UTCEPSS rescore
  27. 2026-08-19 17:02 UTCEPSS rescore
  28. 2026-08-18 13:47 UTCEPSS rescore
  29. 2026-08-17 13:45 UTCEPSS rescore
  30. 2026-08-16 14:55 UTCEPSS rescore
  31. 2026-08-16 02:13 UTCEPSS rescore
  32. 2026-08-15 16:37 UTCOSV refresh
  33. 2026-08-15 01:29 UTCEPSS rescore
  34. 2026-08-13 21:59 UTCEPSS rescore
  35. 2026-08-12 13:49 UTCEPSS rescore
  36. 2026-08-11 13:41 UTCEPSS rescore
  37. 2026-08-10 23:58 UTCEPSS rescore
  38. 2026-08-09 13:45 UTCEPSS rescore
  39. 2026-08-08 16:35 UTCEPSS rescore
  40. 2026-08-07 16:26 UTCEPSS rescore
  41. 2026-08-06 13:45 UTCEPSS rescore
  42. 2026-08-05 19:16 UTCEPSS rescore
  43. 2026-08-04 15:08 UTCEPSS rescore
  44. 2026-08-03 10:35 UTCEPSS rescore
  45. 2026-08-02 02:25 UTCEPSS rescore
  46. 2026-08-02 02:25 UTCEPSS rescore
  47. 2026-08-01 04:14 UTCEPSS rescore
  48. 2026-07-31 08:12 UTCOSV refresh
  49. 2026-07-30 16:26 UTCEPSS rescore
  50. 2026-07-30 16:26 UTCEPSS rescore
  51. 2026-07-28 15:35 UTCEPSS rescore
  52. 2026-07-26 14:53 UTCEPSS rescore
  53. 2026-07-25 14:17 UTCEPSS rescore
  54. 2026-07-25 14:17 UTCEPSS rescore
  55. 2026-07-24 14:16 UTCEPSS rescore
  56. 2026-07-23 14:17 UTCEPSS rescore
  57. 2026-07-23 14:17 UTCEPSS rescore
  58. 2026-07-23 02:44 UTCEG score recompute
  59. 2026-07-22 14:07 UTCEPSS rescore
  60. 2026-07-21 15:23 UTCEPSS rescore
  61. 2026-07-20 17:07 UTCEPSS rescore
  62. 2026-07-19 14:30 UTCEPSS rescore
  63. 2026-07-19 14:30 UTCEPSS rescore
  64. 2026-07-19 02:28 UTCEPSS rescore
  65. 2026-07-19 02:28 UTCEPSS rescore
  66. 2026-07-18 10:03 UTCEPSS rescore
  67. 2026-07-16 17:02 UTCEPSS rescore
  68. 2026-07-15 16:57 UTCEPSS rescore
  69. 2026-07-15 01:59 UTCEPSS rescore
  70. 2026-07-15 01:59 UTCEPSS rescore
  71. 2026-07-13 22:29 UTCEPSS rescore
  72. 2026-07-13 15:38 UTCOSV refresh
  73. 2026-07-13 06:12 UTCEPSS rescore
  74. 2026-07-12 05:45 UTCEPSS rescore
  75. 2026-07-11 08:26 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-56201?
CVE-2024-56201 is a high vulnerability 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 CVE-2024-56201 disclosed?
CVE-2024-56201 was first published on December 23, 2024, with the most recent update on September 22, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (21st 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.

Book a Demo →Browse All CVEs