How severe is CVE-2014-3625?

No CVSS score has been assigned to CVE-2014-3625 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-3625?

CVE-2014-3625 affects the following packages: org.springframework:spring-webmvc (Maven), org.springframework:spring-webmvc (Maven), org.springframework:spring-webmvc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3625?

Update org.springframework:spring-webmvc to 3.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3625 is resolved across your whole dependency graph.

How do I detect CVE-2014-3625 in my Maven dependencies?

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.

How do I mitigate CVE-2014-3625 if there is no patch (or I can't update yet)?

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.

Is CVE-2014-3625 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2014-3625, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-3625?

CVE-2014-3625 has an EPSS (Exploit Prediction Scoring System) score of 9.9%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-3625?

CVE-2014-3625 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-3625 published, and has it been updated?

CVE-2014-3625 was published on November 20, 2014 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2014-3625 — spring-webmvc

Fix: spring-projects/spring-framework@161d3e3

CVE-2014-3625 is a Path Traversal vulnerability in org.springframework:spring-webmvc. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.springframework:spring-webmvc — see the affected versions and patch details below.

Improper Limitation of a Pathname to a Restricted Directory in Spring Framework

Also known asGHSA-hhm4-hwq6-3c6w

Published

Nov 20, 2014

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

9.9%probability of exploitation in next 30 days

Lower Risk-0.40%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc

Real-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

Directory traversal vulnerability in Pivotal Spring Framework 3.0.4 through 3.2.x before 3.2.12, 4.0.x before 4.0.8, and 4.1.x before 4.1.2 allows remote attackers to read arbitrary files via unspecified vectors, related to static resource handling.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-webmvc`	≥ 3.0.4&&< 3.2.12	3.2.12`org.springframework:spring-webmvc:3.2.12`
☕Maven	`org.springframework:spring-webmvc`	≥ 4.0.0&&< 4.0.8	4.0.8`org.springframework:spring-webmvc:4.0.8`
☕Maven	`org.springframework:spring-webmvc`	≥ 4.1.0&&< 4.1.2	4.1.2`org.springframework:spring-webmvc:4.1.2`

Affected Products

2 products · 5 configurations

Application

spring frameworkpivotal_software

≥ 4.1.0 && ≤ 3.1.4

range

Application

spring frameworkvmware

≥ 3.0.4 && ≤ 3.0.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Directory traversal vulnerability in Pivotal Spring Framework 3.0.4 thro…

github.comGithubFeb 2016

Detection & mitigation playbook

Open-source dependency

Detect
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 3.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3625 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.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.1	see advisory	RHSA-2015:0236
Red Hat JBoss BPMS 6.0	`spring`	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	`spring`	RHSA-2015:0235
Red Hat JBoss Fuse Service Works 6.0	`spring`	RHSA-2015:0720

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3625 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works