CVE-2016-6795 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in org.apache.struts:struts2-convention-plugin. A fix is available for org.apache.struts:struts2-convention-plugin — see the affected versions and patch details below.
Path Traversal in Apache Struts
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.struts:struts2-convention-plugin☕org.apache.struts:struts2-convention-pluginReal-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
In Apache Struts 2.3.x before 2.3.31, and 2.5.x before 2.5.5, it is possible to prepare a special URL which will be used for path traversal and execution of arbitrary code on server side. This vulnerability is only exploitable when using the Struts 2 Convention plugin in conjunction with Apache Struts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.struts:struts2-convention-plugin | ≥ 2.3.0&&< 2.3.31 | 2.3.31org.apache.struts:struts2-convention-plugin:2.3.31 |
| ☕Maven | org.apache.struts:struts2-convention-plugin | ≥ 2.5.0&&< 2.5.5 | 2.5.5org.apache.struts:struts2-convention-plugin:2.5.5 |
Affected Products
strutsapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.struts:struts2-convention-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.struts:struts2-convention-plugin to 2.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6795 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.
Frequently Asked Questions
Is CVE-2016-6795 in your dependencies?
Find it across Maven, including transitive dependencies.