CVE-2024-52318 is a medium-severity (CVSS 6.1) CWE-326 vulnerability in org.apache.tomcat:tomcat-jasper. A fix is available for org.apache.tomcat:tomcat-jasper — see the affected versions and patch details below.
Apache Tomcat: Incorrect JSP tag recycling leads to XSS
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 CVE-2024-52318.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.tomcat:tomcat-jasper☕org.apache.tomcat:tomcat-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat.embed:tomcat-embed-jasper☕org.apache.tomcat:tomcat-jasper☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Description:
The fix for improvement 69333 caused pooled JSP tags not to be released after use which in turn could cause output of some tags not to escaped as expected. This unescaped output could lead to XSS.
Versions Affected:
- Apache Tomcat 11.0.0
- Apache Tomcat 10.1.31
- Apache Tomcat 9.0.96
Mitigation:
Users of the affected versions should apply one of the following mitigations:
- Upgrade to Apache Tomcat 11.0.1 or later
- Upgrade to Apache Tomcat 10.1.33 or later Note: 10.1.32 was not released
- Upgrade to Apache Tomcat 9.0.97 or later
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 11.0.0&&< 11.0.1 | 11.0.1org.apache.tomcat:tomcat-jasper:11.0.1 |
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 10.1.31&&< 10.1.32 | 10.1.32org.apache.tomcat:tomcat-jasper:10.1.32 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 9.0.96&&< 9.0.97 | 9.0.97org.apache.tomcat.embed:tomcat-embed-jasper:9.0.97 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 11.0.0&&< 11.0.1 | 11.0.1org.apache.tomcat.embed:tomcat-embed-jasper:11.0.1 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-jasper | ≥ 10.1.31&&< 10.1.32 | 10.1.32org.apache.tomcat.embed:tomcat-embed-jasper:10.1.32 |
| ☕Maven | org.apache.tomcat:tomcat-jasper | ≥ 9.0.96&&< 9.0.97 | 9.0.97org.apache.tomcat:tomcat-jasper:9.0.97 |
Affected Products
tomcatapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-jasper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat-jasper to 11.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52318 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-52318 in your dependencies?
Find it across Maven, including transitive dependencies.