CVE-2024-34064
A public proof of concept exists; no exploitation attested.
- Published2024-05-06
- WeaknessCWE-79
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2024-05-0615:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-34064?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-34064?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 39.x | = 39 | no fix published | NVD |
| 40.x | = 40 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.1 | < 3.1.4 | 3.1.4 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Red Hat Security Advisory: RHUI 4.11 security, bugfix, and enhancement update
Fix
- Vendor fix Red Hat Product Security RHSA-2025:1335 · 2 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions on how to apply this update, see: https://docs.redhat.com/en/documentation/red_hat_update_infrastructure/4/html/migrating_red_hat_update_infrastructure/assembl…
- Workaround from the vendor Red Hat Product Security RHSA-2025:1335 · 255 productsDo not accept user input as keys to the xmlattr filter without validation. See the statement above for more information.
Advisories and patches
- github.comPatch
- github.comVendor Advisory
Detection
read 2026-10-23 19:24 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 7 repositories, unverifiedSandBlastx/flask-vuln-v3SandBlastx/flask-vuln-v4SandBlastx/flask-vuln-baselineSandBlastx/flask-vuln-v1SandBlastx/flask-vuln-v2 PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2024-05-09
- OpenCVESSVC decisionnone—
- CISA-ADPCVSS 3.15.42024-05-09
- CNACVSS 3.15.4read 2026-10-23
- CNAweakness (CWE)CWE-79read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-10-22
- PoC-in-GitHubproof of concept7read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
- Published
- 2024-05-06
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2024-34064?
Is CVE-2024-34064 actively exploited?
What is the CVSS score for CVE-2024-34064?
Running RHUI 4.11 security, bugfix,? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.