CVE-2024-56326

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
7.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.5%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Jinja is an extensible templating engine. Prior to 3.1.5, An oversight in how the Jinja sandboxed environment detects calls to str.format allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the content 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. Jinja's sandbox does catch calls to str.format and ensures they don't escape the sandbox. However, it's possible to store a reference to a malicious string's format method, then pass that to a filter that calls it. No such filters are built-in to Jinja, but could be present through custom filters in an application. After the fix, such indirect calls are also handled by the sandbox. This vulnerability is fixed in 3.1.5.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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.
Exploitation0.5% × 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.5%
EPSS %ILE
42nd
KEV
Not listed

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.

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

November 3, 2025

Advisory Details (4)

Auto-updated Oct 11, 2026
Patch available. Sources: github_commit, github_release, github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4126-1] jinja2 security update

https://lists.debian.org/debian-lts-announce/2025/04/msg00022.html
GitHub advisoryMentions a patch (unverified)

Sandbox breakout through indirect reference to format method · Advisory · pallets/jinja · GitHub

https://github.com/pallets/jinja/security/advisories/GHSA-q2x7-8rv6-6q7h
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
GitHub commit Patch Available

commit 48b0687e05a5 (pallets/jinja)

Patch available: pallets/jinja 3.1.5 (contains commit 48b0687e05a5)

https://github.com/pallets/jinja/commit/48b0687e05a5466a91cd5812d604fa37ad0943b4

Vendor Advisories for CVE-2024-56326(20)

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

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-jinja2-0:3.1.5-1.el9pc2025-05-06redhat
redhatrhdh/rhdh-hub-rhel9:1.52025-03-27redhat
redhatopenshift4/ose-ansible-operator:v4.13.0-202503111300.p0.g01bfabb.assembly.stream.el82025-03-20redhat
redhatpython-jinja2-0:2.10.1-2.el8_2.32025-03-11redhat
redhatopenshift4/ose-ansible-operator:v4.15.0-202502171304.p0.g52fc4b9.assembly.stream.el82025-02-27redhat
redhatopenstack-ansible-core-0:2.14.2-4.6.el9ost2025-02-25redhat
redhatopenshift4/ose-ansible-operator:v4.12.0-202502040858.p0.g0bd975e.assembly.stream.el82025-02-13redhat
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
redhatpython-jinja2-0:2.7.2-5.el7_92025-02-10redhat
redhatpython-jinja2-0:2.10.1-2.el8_4.12025-02-06redhat
redhatansible-automation-platform/ee-minimal-rhel9:2.15.13-102025-02-05redhat
redhatopenshift4/ose-ansible-rhel9-operator:v4.17.0-202501300634.p0.g9cb5839.assembly.stream.el92025-02-05redhat
redhatpython-jinja2-0:2.11.3-4.el9_0.12025-02-04redhat
redhatpython-jinja2-0:2.10.1-4.el8_6.12025-02-04redhat
redhatpython-jinja2-0:2.11.3-4.el9_2.12025-02-04redhat
redhatpython-jinja2-0:2.10.1-4.el8_8.12025-02-03redhat
redhatpython-jinja2-0:2.11.3-6.el9_42025-01-30redhat
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.el92025-01-28redhat
redhatansible-automation-platform-24/lightspeed-rhel8-operator:2.4-332025-01-27redhat
redhatpython-jinja2-0:2.10.1-6.el8_102025-01-27redhat
redhatpython-jinja2-0:3.1.5-1.el9ap2025-01-27redhat

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

(12 across 12 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:11(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.11.3-1, 2.11.3-1+deb11u1, 2.11.3-1+deb11u2
  • every version up to 2.11.3-1+deb11u3: fixed in 2.11.3-1+deb11u3
—
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
jinja22.0 ... 3.1.4 (50 versions)
  • every version up to 3.1.5: fixed in 3.1.5
—

Weakness Classification(2)

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

Additional Vendor Advisories

(22)

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

Showing the most recent 90 of 182 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2024-56326?
CVE-2024-56326 is a high-severity vulnerability; its CVE record was published on December 23, 2024. Jinja is an extensible templating engine. Prior to 3.1.5, An oversight in how the Jinja sandboxed environment detects calls to str.format allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the…
When was the CVE record for CVE-2024-56326 published?
The CVE record for CVE-2024-56326 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-56326 actively exploited?
CVE-2024-56326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56326?
CVE-2024-56326 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56326?
A fix for CVE-2024-56326 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56326 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-56326

Explore →

Is Your Infrastructure Affected by CVE-2024-56326?

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

Book a Demo →Browse All CVEs