How severe is CVE-2014-3578?

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

Which packages are affected by CVE-2014-3578?

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

How do I fix CVE-2014-3578?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-3578 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-3578 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3578 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2014-3578 has an EPSS (Exploit Prediction Scoring System) score of 6.4%, placing it in the 94th 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-3578?

CVE-2014-3578 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-3578 published, and has it been updated?

CVE-2014-3578 was published on February 19, 2015 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-3578 — spring-core

Fix: spring-projects/spring-framework@748167b

CVE-2014-3578 is a Path Traversal vulnerability in org.springframework:spring-core. A fix is available for org.springframework:spring-core — see the affected versions and patch details below.

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

Also known asGHSA-rhcg-rwhx-qj3j

Published

Feb 19, 2015

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.springframework:spring-core☕org.springframework:spring-core

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.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-core`	≥ 3.0.0&&< 3.2.9	3.2.9`org.springframework:spring-core:3.2.9`
☕Maven	`org.springframework:spring-core`	≥ 4.0.0&&< 4.0.5	4.0.5`org.springframework:spring-core:4.0.5`

Affected Products

1 product · 2 configurations

Application

spring frameworkpivotal_software

≥ 4.0.0 && < 4.0.5

range

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-core to 3.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3578 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 BPMS 6.0	`spring`	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	`spring`	RHSA-2015:0235
Red Hat JBoss Data Virtualization 6.1	see advisory	RHSA-2015:0675
Red Hat JBoss Fuse Service Works 6.0	`spring`	RHSA-2015:0720

Frequently Asked Questions

Directory traversal vulnerability in Pivotal Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.

O3 Security · Impact-Aware SCA

Is CVE-2014-3578 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works