CVE-2026-22737 — spring-webmvc
MEDIUMCVE-2026-22737 is a medium-severity (CVSS 5.9) Path Traversal vulnerability in org.springframework:spring-webmvc. A fix is available for org.springframework:spring-webmvc — see the affected versions and patch details below.
Spring Framework Improper Path Limitation with Script View Templates
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-2026-22737.
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.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webflux☕org.springframework:spring-webfluxReal-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
Use of Java scripting engine enabled (e.g. JRuby, Jython) template views in Spring MVC and Spring WebFlux applications can result in disclosure of content from files outside the configured locations for script template views. This issue affects Spring Framework: from 7.0.0 through 7.0.5, from 6.2.0 through 6.2.16, from 6.1.0 through 6.1.25, from 5.3.0 through 5.3.46.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-webmvc | ≥ 7.0.0-M1&&< 7.0.6 | 7.0.6org.springframework:spring-webmvc:7.0.6 |
| ☕Maven | org.springframework:spring-webmvc | ≥ 6.2.0&&< 6.2.17 | 6.2.17org.springframework:spring-webmvc:6.2.17 |
| ☕Maven | org.springframework:spring-webmvc | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-webmvc | ≥ 5.3.0 | No fix |
| ☕Maven | org.springframework:spring-webflux | ≥ 7.0.0-M1&&< 7.0.6 | 7.0.6org.springframework:spring-webflux:7.0.6 |
| ☕Maven | org.springframework:spring-webflux | ≥ 6.2.0&&< 6.2.17 | 6.2.17org.springframework:spring-webflux:6.2.17 |
Affected Products
spring frameworkvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-webmvc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-webmvc to 7.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22737 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
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.
To mitigate this issue, avoid using Java scripting engine enabled template views (e.g., JRuby, Jython) in Spring MVC and Spring WebFlux applications. If these engines are not essential for application functionality, disable or remove their integration to prevent unauthorized file disclosure. Review application configurations to ensure that template view directories are strictly controlled and that no external scripting engines are inadvertently enabled.Source: Red Hat security advisory for CVE-2026-22737 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-22737 in your dependencies?
Find it across Maven, including transitive dependencies.