How severe is CVE-2014-0050?

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

Which packages are affected by CVE-2014-0050?

CVE-2014-0050 affects the following packages: commons-fileupload:commons-fileupload (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0050?

Update commons-fileupload:commons-fileupload to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0050 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2014-0050 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 CVE-2014-0050?

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

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

Yes. There are 3 known exploit references for CVE-2014-0050, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations 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-0050?

CVE-2014-0050 has an EPSS (Exploit Prediction Scoring System) score of 83.2%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-0050?

CVE-2014-0050 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2014-0050 was published on April 1, 2014 and was last updated on April 16, 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-0050 — commons-fileupload

CVE-2014-0050 is a CWE-264 vulnerability in commons-fileupload:commons-fileupload. 3 public exploit references exist, so weaponization risk is real. A fix is available for commons-fileupload:commons-fileupload — see the affected versions and patch details below.

Commons FileUpload Denial of service vulnerability

Also known asGHSA-xx68-jfcg-xmmf

Published

Apr 1, 2014

Updated

Apr 16, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

83.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% 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

☕commons-fileupload:commons-fileupload☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

MultipartStream.java in Apache Commons FileUpload before 1.3.1, as used in Apache Tomcat, JBoss Web, and other products, allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted Content-Type header that bypasses a loop's intended exit conditions.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-fileupload:commons-fileupload`	all versions	1.3.1`commons-fileupload:commons-fileupload:1.3.1`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0-RC1&&< 8.0.3	8.0.3`org.apache.tomcat:tomcat:8.0.3`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.52	7.0.52`org.apache.tomcat:tomcat:7.0.52`

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.

EDB-31615dosmultiple✓ Verified

Apache Commons FileUpload and Apache Tomcat - Denial of Service

by Trustwave's SpiderLabs · Feb 12, 2014

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-fileupload:commons-fileupload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update commons-fileupload:commons-fileupload to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0050 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 CVE-2014-0050 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-0050. 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
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2014:0452
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-64.el6_5`	RHSA-2014:0429
Red Hat JBoss A-MQ 6.1	see advisory	RHSA-2014:0401
Red Hat JBoss BPMS 6.0	`jbossweb`	RHSA-2014:0373
Red Hat JBoss Enterprise Application Platform 6.2	`jbossweb`	RHSA-2014:0252
Red Hat JBoss Enterprise Application Platform 6.2 for RHEL 5	`jbossweb-0:7.3.0-2.Final_redhat_2.1.ep6.el5`	RHSA-2014:0253
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`tomcat6-0:6.0.37-19_patch_04.ep6.el5`	RHSA-2014:0525
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`tomcat7-0:7.0.40-13_patch_02.ep6.el5`	RHSA-2014:0526

Ubuntu

USN-2130-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0050 in your dependencies?

O3 Security finds CVE-2014-0050 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