BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-56326High confidence

Jinja has a sandbox breakout through indirect reference to format method

pallets · jinja

Official source article: GitHub GHSA-Q2X7-8RV6-6Q7H ↗. Check the applicable product and release in the original source.

5.4MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 3 Nov 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.52% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs pallets jinja and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcejinja2Vendor fix publishedDebian records a fixed source-package version for this release.3.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcejinja2Vendor fix publishedDebian records a fixed source-package version for this release.3.1.2-1+deb12u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcejinja2Vendor fix publishedDebian records a fixed source-package version for this release.3.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcejinja2Vendor fix publishedDebian records a fixed source-package version for this release.3.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejinja2Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.1.2-1ubuntu1.2Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIjinja2ECOSYSTEM: introduced 0; fixed 3.1.53.1.5OSV record ↗aggregator derived · 10 Sep 2026
pipjinja2<= 3.1.43.1.5GitHub advisory ↗upstream repository advisory · 3 Nov 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-56326 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjinja2: Jinja has a sandbox breakout through indirect reference to format method
32 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-lightspeed-tech-preview/lightspeed-service-api-rhel9.src as a component of OpenShift Lightspeed
  • aap-cloud-metrics-collector-container as a component of Red Hat Ansible Automation Platform 2
  • python-jinja2 as a component of Red Hat Enterprise Linux 6
  • python-jinja2.src as a component of Red Hat Enterprise Linux 6
  • rhel9/keylime-registrar.src as a component of Red Hat Enterprise Linux 9
  • rhelai1/bootc-amd-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-aws-nvidia-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-azure-amd-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-azure-nvidia-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-gcp-nvidia-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-ibm-nvidia-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
  • rhelai1/bootc-intel-rhel9.src as a component of Red Hat Enterprise Linux AI (RHEL AI)
Summary
A flaw was found in the Jinja package. In affected versions of Jinja, 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 that execute untrusted templates. Jinja's sandbox does catch calls to str.format and ensures they don't escape the sandbox. However, storing a reference to a malicious string's format method is possible, then passing that to a filter that calls it. No such filters are built into Jinja but could be present through custom filters in an application. After the fix, such indirect calls are also handled by the sandbox.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-3607

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Neutralization of Special Elements Used in a Template Engine → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-1336 ↗

CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-1336
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0054Red Hat Enterprise Linux (Jinja): Mehrere Schwachstellen ermöglichen Codeausführung

Ein lokaler Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux, Red Hat Ansible Automation Platform und Red Hat OpenShift ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241225Security Bulletin 25 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Dec 2024, published on 25 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2024-37890 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 Référence CVE CVE-2024-4068 https://www.cve.org/CVERecord?id=CVE-2024-4068 Référence CVE CVE-2024-43796 https://www.cve.org/CVERecord?id=CVE-2024-43796 Référence CVE CVE-2024-43799 https://www.cve.org/CVERecord?id=CVE-2024-43799 Référence CVE CVE-2024-43800 https://www.cve.org/CVERecord?id=CVE-2024-43800 Référence CVE CVE-2024-45590 https://www.cve.org/CVERecord?id=CVE-2024-45590 Référence CVE CVE-2024-47764 https://www.cve.org/CVERecord?id=CVE-2024-47764 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2025-12816 https://www.cve.org/CVERecord?id=CVE-2025-12816 Référence CVE CVE-2025-13466 https://www.cve.org/CVERecord?id=CVE-2025-13466 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-30359 https://www.cve.org/CVERecord?id=CVE-2025-30359 Référence CVE CVE-2025-30360 https://www.cve.org/CVERecord?id=CVE-2025-30360 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2025-66031 Référence CVE CVE-2025-68146 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53687 https://www.cve.org/CVERecord?id=CVE-2024-53687 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE-2024-5569 Référence CVE CVE-2024-56180 https://www.cve.org/CVERecord?id=CVE-2024-56180 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56368 https://www.cve.org/CVERecord?id=CVE-2024-56368 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56544 https://www.cve.org/CVERecord?id=CVE-2024-56544 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56565 https://www.cve.org/CVERecord?id=CVE-2024-56565 Référence CVE CVE-2024-56566 https://www.cve.org/CVERecord?id=CVE-2024-56566 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53687 https://www.cve.org/CVERecord?id=CVE-2024-53687 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE-2024-5569 Référence CVE CVE-2024-56180 https://www.cve.org/CVERecord?id=CVE-2024-56180 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56368 https://www.cve.org/CVERecord?id=CVE-2024-56368 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56544 https://www.cve.org/CVERecord?id=CVE-2024-56544 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56565 https://www.cve.org/CVERecord?id=CVE-2024-56565 Référence CVE CVE-2024-56566 https://www.cve.org/CVERecord?id=CVE-2024-56566 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1043Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0760Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-49828 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-51473 https://www.cve.org/CVERecord?id=CVE-2024-51473 Référence CVE CVE-2024-51479 https://www.cve.org/CVERecord?id=CVE-2024-51479 Référence CVE CVE-2024-51504 https://www.cve.org/CVERecord?id=CVE-2024-51504 Référence CVE CVE-2024-52894 https://www.cve.org/CVERecord?id=CVE-2024-52894 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56332 https://www.cve.org/CVERecord?id=CVE-2024-56332 Référence CVE CVE-2024-56339 https://www.cve.org/CVERecord?id=CVE-2024-56339 Référence CVE CVE-2024-57699 https://www.cve.org/CVERecord?id=CVE-2024-57699 Référence CVE CVE-2024-6484 https://www.cve.org/CVERecord?id=CVE-2024-6484 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2024-6762 https://www.cve.org/CVERecord?id=CVE-2024-6762 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-6827 https://www.cve.org/CVERecord?id=CVE-2024-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0538Multiples vulnérabilités dans VMware Tanzu

ecord?id=CVE-2024-42367 Référence CVE CVE-2024-43497 https://www.cve.org/CVERecord?id=CVE-2024-43497 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-5206 https://www.cve.org/CVERecord?id=CVE-2024-5206 Référence CVE CVE-2024-52304 https://www.cve.org/CVERecord?id=CVE-2024-52304 Référence CVE CVE-2024-53899 https://www.cve.org/CVERecord?id=CVE-2024-53899 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE-2024-5569 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-5998 https://www.cve.org/CVERecord?id=CVE-2024-5998 Référence CVE CVE-2024-7804 https://www.cve.org/CVERecord?id=CVE-2024-7804 Référence CVE CVE-2024-8309 https://www.cve.org/CVERecord?id=CVE-2024-8309 Référence CVE CVE-2025-1094 https://www.cve.org/CVERecord?id=CVE-2025-1094 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-4207 https://www.cve.org/CVERecord?id=CVE-2025-4207 Gestion détaillée du document le 26 juin 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Con

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0481Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-47764 Référence CVE CVE-2024-49766 https://www.cve.org/CVERecord?id=CVE-2024-49766 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-50379 https://www.cve.org/CVERecord?id=CVE-2024-50379 Référence CVE CVE-2024-52304 https://www.cve.org/CVERecord?id=CVE-2024-52304 Référence CVE CVE-2024-52316 https://www.cve.org/CVERecord?id=CVE-2024-52316 Référence CVE CVE-2024-52317 https://www.cve.org/CVERecord?id=CVE-2024-52317 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56332 https://www.cve.org/CVERecord?id=CVE-2024-56332 Référence CVE CVE-2024-56337 https://www.cve.org/CVERecord?id=CVE-2024-56337 Référence CVE CVE-2024-57556 https://www.cve.org/CVERecord?id=CVE-2024-57556 Référence CVE CVE-2024-9902 https://www.cve.org/CVERecord?id=CVE-2024-9902 Référence CVE CVE-2025-1334 https://www.cve.org/CVERecord?id=CVE-2025-1334 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-22235 https://www.cve.org/CVERecord?id=CVE-2025-22235 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0422Multiples vulnérabilités dans IBM QRadar SIEM

ord?id=CVE-2024-10963 Référence CVE CVE-2024-11168 https://www.cve.org/CVERecord?id=CVE-2024-11168 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-47072 https://www.cve.org/CVERecord?id=CVE-2024-47072 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2025-24855 https://www.cve.org/CVERecord?id=CVE-2025-24855 Gestion détaillée du document le 16 mai 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0401Multiples vulnérabilités dans Juniper Networks Secure Analytics

d?id=CVE-2024-47668 Référence CVE CVE-2024-50302 https://www.cve.org/CVERecord?id=CVE-2024-50302 Référence CVE CVE-2024-50379 https://www.cve.org/CVERecord?id=CVE-2024-50379 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-52337 https://www.cve.org/CVERecord?id=CVE-2024-52337 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53677 https://www.cve.org/CVERecord?id=CVE-2024-53677 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56337 https://www.cve.org/CVERecord?id=CVE-2024-56337 Référence CVE CVE-2024-56463 https://www.cve.org/CVERecord?id=CVE-2024-56463 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-7348 https://www.cve.org/CVERecord?id=CVE-2024-7348 Référence CVE CVE-2024-8508 https://www.cve.org/CVERecord?id=CVE-2024-8508 Référence CVE CVE-2024-9823 https://www.cve.org/CVERecord?id=CVE-2024-9823 Référence CVE CVE-2025-0624 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0337Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-45336 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45813 https://www.cve.org/CVERecord?id=CVE-2024-45813 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-47554 https://www.cve.org/CVERecord?id=CVE-2024-47554 Référence CVE CVE-2024-48948 https://www.cve.org/CVERecord?id=CVE-2024-48948 Référence CVE CVE-2024-52798 https://www.cve.org/CVERecord?id=CVE-2024-52798 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-57699 https://www.cve.org/CVERecord?id=CVE-2024-57699 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6531 https://www.cve.org/CVERecord?id=CVE-2024-6531 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2025-1094 https://www.cve.org/CVERecord?id=CVE-2025-1094 Référence CVE CVE-2025-1302 https://www.cve.org/CVERecord?id=CVE-2025-1302

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0309Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36974 https://www.cve.org/CVERecord?id=CVE-2024-36974 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49766 https://www.cve.org/CVERecord?id=CVE-2024-49766 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-7553 https://www.cve.org/CVERecord?id=CVE-2024-7553 Référence CVE CVE-2024-8207 https://www.cve.org/CVERecord?id=CVE-2024-8207 Gestion détaillée du document le 11 avril 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0272Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0154Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-28780 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-38999 https://www.cve.org/CVERecord?id=CVE-2024-38999 Référence CVE CVE-2024-40642 https://www.cve.org/CVERecord?id=CVE-2024-40642 Référence CVE CVE-2024-45081 https://www.cve.org/CVERecord?id=CVE-2024-45081 Référence CVE CVE-2024-45084 https://www.cve.org/CVERecord?id=CVE-2024-45084 Référence CVE CVE-2024-50379 https://www.cve.org/CVERecord?id=CVE-2024-50379 Référence CVE CVE-2024-52337 https://www.cve.org/CVERecord?id=CVE-2024-52337 Référence CVE CVE-2024-52902 https://www.cve.org/CVERecord?id=CVE-2024-52902 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-56337 https://www.cve.org/CVERecord?id=CVE-2024-56337 Référence CVE CVE-2024-8508 https://www.cve.org/CVERecord?id=CVE-2024-8508 Référence CVE CVE-2024-9823 https://www.cve.org/CVERecord?id=CVE-2024-9823 Gestion détaillée du document le 21 février 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sys

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0106Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-50279 Référence CVE CVE-2024-50282 https://www.cve.org/CVERecord?id=CVE-2024-50282 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-53047 https://www.cve.org/CVERecord?id=CVE-2024-53047 Référence CVE CVE-2024-53064 https://www.cve.org/CVERecord?id=CVE-2024-53064 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53677 https://www.cve.org/CVERecord?id=CVE-2024-53677 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE-2024-5569 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-7348 https://www.cve.org/CVERecord?id=CVE-2024-7348 Gestion détaillée du document le 07 février 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028259Pallets project の Jinja における保護メカニズムの不具合に関する脆弱性

Pallets project の Jinja には、保護メカニズムの不具合に関する脆弱性、テンプレートエンジンで使用される特殊な要素の不適切な無効化に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 23 Dec 2024 · Last source change 3 Nov 2025, 19:32 UTC · CWE-1336 · Improper Neutralization of Special Elements Used in a Template Engine

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-3607
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.1.5 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 3.1.5 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-3607↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-Q2X7-8RV6-6Q7H↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-56326 · cve.blacktree.nl