GHSA-h5c8-rqwp-cp95 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in jinja2. A fix is available for jinja2 — see the affected versions and patch details below.
Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h5c8-rqwp-cp95.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-h5c8-rqwp-cp95 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
jinja2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
The xmlattr filter in affected versions of Jinja accepts keys containing spaces. XML/HTML attributes cannot contain spaces, as each would then be interpreted as 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. Note that accepting keys as user input is not common or a particularly intended use case of the xmlattr filter, and an application doing so should already be verifying what keys are provided regardless of this fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | jinja2 | all versions | 3.1.3pip install --upgrade 'jinja2==3.1.3' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jinja2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jinja2 to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5c8-rqwp-cp95 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h5c8-rqwp-cp95 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h5c8-rqwp-cp95. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The identified issue is classified as moderate due to a cross-site scripting (XSS) vulnerability in Jinja2. This flaw arises from the xmlattr filter, which permits keys with spaces, contrary to XML/HTML attribute standards. In scenarios where an application accepts user-input keys and renders them for other users,…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | python3x-jinja2-0:3.1.3-1.el8ap | RHSA-2024:1057 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | automation-controller-0:4.5.5-2.el8ap | RHSA-2024:1640 |
| Red Hat Ceph Storage 7.1 | rhceph/ceph-nvmeof-cli-rhel9:1.2.13-4 | RHSA-2024:3927 |
| Red Hat Enterprise Linux 8 | fence-agents-0:4.2.1-121.el8_9.4 | RHBA-2024:0891 |
| Red Hat Enterprise Linux 8 | fence-agents-0:4.2.1-129.el8 | RHSA-2024:2968 |
| Red Hat Enterprise Linux 8 | python27:2.7-8100020240208011952.5f0f67de | RHSA-2024:2987 |
| Red Hat Enterprise Linux 8 | python-jinja2-0:2.10.1-4.el8 | RHSA-2024:3102 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | fence-agents-0:4.2.1-65.el8_4.14 | RHBA-2024:1398 |
Frequently Asked Questions
Is GHSA-h5c8-rqwp-cp95 in your dependencies?
O3 Security finds GHSA-h5c8-rqwp-cp95 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.