CVE-2024-22195

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.9% (57th 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Jinja is an extensible templating engine. Special placeholders in the template allow writing code similar to Python syntax. It is possible to inject arbitrary HTML attributes into the rendered HTML template, potentially leading to Cross-Site Scripting (XSS). The Jinja xmlattr filter can be abused to inject arbitrary HTML attribute keys and values, bypassing the auto escaping mechanism and potentially leading to XSS. It may also be possible to bypass attribute validation checks if they are blacklist-based.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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
Severity54% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

January 11, 2024

Last Modified

November 3, 2025

References (13)

Vendor Advisories for CVE-2024-22195(9)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jinja2 (3.1.2-1ubuntu0.23.10.1) @ mantic2026-05-24ubuntu
redhatrhceph/snmp-notifier-rhel9:1.2.1-672024-06-13redhat
redhatpython-jinja2-0:2.10.1-4.el82024-05-22redhat
redhatopenstack-ansible-core-0:2.14.2-4.3.el9ost2024-05-22redhat
redhatpython27:2.7-8100020240208011952.5f0f67de2024-05-22redhat
redhatfence-agents-0:4.2.1-129.el82024-05-22redhat
redhatfence-agents-0:4.10.0-62.el92024-04-30redhat
redhatpython-jinja2-0:2.11.3-5.el92024-04-30redhat
redhatpython-jinja2-0:3.1.3-1.el8pc2024-04-23redhat
redhatpython-jinja2-0:3.1.3-1.el8ui2024-04-18redhat
redhatautomation-controller-0:4.5.5-2.el9ap2024-04-02redhat
redhatpython-jinja2-0:3.1.3-0.1.el8pc2024-03-27redhat
redhatfence-agents-0:4.10.0-20.el9_0.112024-03-05redhat
redhatpython-jinja2-0:3.1.3-1.el9ap2024-02-29redhat

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

(14 across 14 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.4-r0: fixed in 3.1.4-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.4-r0: fixed in 3.1.4-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.4-r0: fixed in 3.1.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.3-r0: fixed in 3.1.3-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.10-2
  • every version up to 2.10-2+deb10u1: fixed in 2.10-2+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.11.3-1
  • every version up to 2.11.3-1+deb11u1: fixed in 2.11.3-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jinja23.1.2-1
  • every version up to 3.1.2-1+deb12u1: fixed in 3.1.2-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.3-1: fixed in 3.1.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.3-1: fixed in 3.1.3-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.0 ... 3.1.2 (48 versions)
  • every version up to 3.1.3: fixed in 3.1.3
—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

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 7× in last 7d / 24× 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 181 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2024-22195?
CVE-2024-22195 is a medium vulnerability published on January 11, 2024. Jinja is an extensible templating engine. Special placeholders in the template allow writing code similar to Python syntax. It is possible to inject arbitrary HTML attributes into the rendered HTML template, potentially leading to Cross-Site Scripting (XSS). The Jinja xmlattr filter can be abused…
When was CVE-2024-22195 disclosed?
CVE-2024-22195 was first published on January 11, 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-22195 actively exploited?
CVE-2024-22195 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-22195?
CVE-2024-22195 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2024-22195?
A fix for CVE-2024-22195 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-22195 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-22195

Explore →

Is Your Infrastructure Affected by CVE-2024-22195?

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

Book a Demo →Browse All CVEs