GHSA-f632-9449-3j4w 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 - XSS in generated JSPs
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-f632-9449-3j4w.
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-f632-9449-3j4w 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 379,145 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
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 |
Detection & 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 GHSA-f632-9449-3j4w 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-f632-9449-3j4w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f632-9449-3j4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f632-9449-3j4w in your dependencies?
O3 Security finds GHSA-f632-9449-3j4w across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.