CVE-2024-56326

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 31% of all CVEs by exploit prediction. 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
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.8Exploit: NoneExposed: 0

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.8(medium)
EPSS
39.5%
KEV
Not listed

Published

December 23, 2024

Last Modified

November 3, 2025

References (4)

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 / EcosystemFixed in / 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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
jinja22.0 ... 3.1.4 (50 versions)3.1.5—

Weakness Classification(2)

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

Additional Vendor Advisories

(19)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-56326?
CVE-2024-56326 is a high vulnerability 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 CVE-2024-56326 disclosed?
CVE-2024-56326 was first published in the National Vulnerability Database on December 23, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56326 actively exploited?
CVE-2024-56326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56326, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs