How severe is GHSA-hhm4-hwq6-3c6w?

No CVSS score has been assigned to GHSA-hhm4-hwq6-3c6w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hhm4-hwq6-3c6w?

GHSA-hhm4-hwq6-3c6w 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 GHSA-hhm4-hwq6-3c6w?

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 GHSA-hhm4-hwq6-3c6w is resolved across your whole dependency graph.

How do I detect GHSA-hhm4-hwq6-3c6w 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 GHSA-hhm4-hwq6-3c6w if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-hhm4-hwq6-3c6w?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hhm4-hwq6-3c6w can be triaged on real exposure rather than presence alone.

Is GHSA-hhm4-hwq6-3c6w actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-hhm4-hwq6-3c6w, 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 GHSA-hhm4-hwq6-3c6w?

GHSA-hhm4-hwq6-3c6w has an EPSS (Exploit Prediction Scoring System) score of 10.3%, placing it in the 95th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-hhm4-hwq6-3c6w?

GHSA-hhm4-hwq6-3c6w 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 GHSA-hhm4-hwq6-3c6w published, and has it been updated?

GHSA-hhm4-hwq6-3c6w was published on May 13, 2022 and was last updated on December 3, 2024. 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

GHSA-hhm4-hwq6-3c6w — spring-webmvc

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

GHSA-hhm4-hwq6-3c6w is a Path Traversal vulnerability in org.springframework:spring-webmvc. 2 public exploit references exist, 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 asCVE-2014-3625

Published

May 13, 2022

Updated

Dec 3, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

10.3%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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.

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`

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 GHSA-hhm4-hwq6-3c6w 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-hhm4-hwq6-3c6w can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hhm4-hwq6-3c6w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-hhm4-hwq6-3c6w in your dependencies?

O3 Security finds GHSA-hhm4-hwq6-3c6w across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works