Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-34064: Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter

Noroxi assessment

Priority: Monitor (action score 21/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: pallets jinja 3.1.4; azl3 nodejs 20.14.0-1 on Azure Linux 3.0 20.14.0-1; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-1.

Low priority for now. Upgrade to pallets jinja 3.1.4; azl3 nodejs 20.14.0-1 on Azure Linux 3.0 20.14.0-1; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Jinja is an extensible templating engine. The `xmlattr` filter in affected versions of Jinja accepts keys containing non-attribute characters. XML/HTML attributes cannot contain spaces, `/`, `>`, or `=`, as each would then be interpreted as starting a separate attribute. If an application accepts keys (as opposed to only values) as user input, and renders these in pages that other users see as well, an attacker could use this to inject other attributes and perform XSS. The fix for CVE-2024-22195 only addressed spaces but not other characters. Accepting keys as user input is now explicitly considered an unintended use case of the `xmlattr` filter, and code that does so without otherwise validating the input should be flagged as insecure, regardless of Jinja version. Accepting _values_ as user input continues to be safe. This vulnerability is fixed in 3.1.4.

MediumCVSS 5.4 · v3.1—Proof of concept Fix available
Published
May 6, 2024
Updated
Jun 17, 2026
EPSS
0.9% · 62th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-34064

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for palletsprojects records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
palletsprojectsjinja
fedoraprojectfedora

Limit the impact of XSS

This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.

Check security headers

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora39
  • fedoraproject fedora40
  • palletsprojects jinjabefore 3.1.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • pallets jinja

    • < 3.1.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8python3-jinja2before 2.10.1-5.el8_102.10.1-5.el8_10
AlmaLinux:9fence-agents-aliyunbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-allbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-amt-wsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-apcbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-apc-snmpbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-awsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-azure-armbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-bladecenterbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-brocadebefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-cisco-mdsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-cisco-ucsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-commonbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-computebefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-drac5before 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-eaton-snmpbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-emersonbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-epsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-gcebefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-heuristics-pingbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-hpbladebefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-ibm-powervsbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-ibm-vpcbefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3
AlmaLinux:9fence-agents-ibmbladebefore 4.10.0-62.el9_4.34.10.0-62.el9_4.3

+96

Same product

palletsprojects: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-10745In Pallets Jinja before 2.8.1, str.format allows a sandbox escape.
    35Monitor
  • CVE-2019-10906In Pallets Jinja before 2.10.1, str.format_map allows a sandbox escape.
    35Monitor
  • CVE-2024-22195Jinja vulnerable to Cross-Site Scripting (XSS)
    24Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-28493Feb 1, 2021 · Regular Expression Denial of Service (ReDoS)
    22Monitor
  • Later →CVE-2024-56201Dec 23, 2024 · Jinja has a sandbox breakout through malicious filenames
    21Monitor
  • Later →CVE-2024-56326Dec 23, 2024 · Jinja has a sandbox breakout through indirect reference to format method
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
pallets jinja3.1.4 · descriptionVendor (CNA)
azl3 nodejs 20.14.0-1 on Azure Linux 3.020.14.0-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 nodejs 20.14.0-8 on Azure Linux 3.020.14.0-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 python-jinja2 3.1.2-2 on Azure Linux 3.03.1.2-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 python-jinja2 3.1.2-3 on Azure Linux 3.03.1.2-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 nodejs18 18.20.3-4 on CBL Mariner 2.018.20.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 nodejs18 18.20.3-5 on CBL Mariner 2.018.20.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 nodejs18 18.20.3-5 on CBL-Mariner 2.018.20.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 python-jinja2 3.0.3-4 on CBL Mariner 2.03.0.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 python-jinja2 3.0.3-7 on CBL Mariner 2.03.0.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 python-jinja2 3.0.3-7 on CBL-Mariner 2.03.0.3-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:fence-agents-aliyun4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-all4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-amt-ws4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-apc4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-apc-snmp4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-aws4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-azure-arm4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-bladecenter4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-brocade4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-cisco-mds4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-cisco-ucs4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
almalinux:fence-agents-common4.10.0-62.el9_4.3 · AlmaLinux:9Package registry (OSV)
alpine:py3-jinja23.1.4-r0 · Alpine:v3.17Package registry (OSV)
debian:jinja23.1.2-1+deb12u1 · Debian:12Package registry (OSV)
opensuse:python-Jinja22.10.1-150000.3.13.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
PyPI:jinja23.1.4Package registry (OSV)
red hat:automation-controller-venv-tower0:4.5.7-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python-cryptography0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9Package registry (OSV)
red hat:python-cryptography-debugsource0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9Package registry (OSV)

+12

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×7

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-03-09
Proof-of-concept repository on GitHubstars:02026-03-09
Proof-of-concept repository on GitHubstars:02026-03-09
Proof-of-concept repository on GitHubstars:02026-03-09
Proof-of-concept repository on GitHubstars:02026-03-09
Proof-of-concept repository on GitHubstars:02026-03-10
Proof-of-concept repository on GitHubstars:02026-03-10

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+672 d
  3. TodayNov 1, 2026+909 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-22195117 days apartJinja vulnerable to Cross-Site Scripting (XSS)
    24Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

The bug in code

The whole CWE-79 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records