How severe is CVE-2016-1000031?

CVE-2016-1000031 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-1000031?

CVE-2016-1000031 affects the following packages: commons-fileupload:commons-fileupload (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-1000031?

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

How do I detect CVE-2016-1000031 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-2016-1000031 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2016-1000031 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-1000031 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-2016-1000031?

CVE-2016-1000031 has an EPSS (Exploit Prediction Scoring System) score of 32.7%, placing it in the 98th 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 CVE-2016-1000031?

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

When was CVE-2016-1000031 published, and has it been updated?

CVE-2016-1000031 was published on October 25, 2016 and was last updated on October 24, 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

CRITICAL severity

CVE-2016-1000031 — commons-fileupload

CRITICAL

CVE-2016-1000031 is a critical-severity (CVSS 9.8) CWE-284 vulnerability in commons-fileupload:commons-fileupload. EPSS puts its 30-day exploitation probability at 32.7% (98th percentile). A fix is available for commons-fileupload:commons-fileupload — see the affected versions and patch details below.

Improper Access Control in commons-fileupload

Also known asGHSA-7x9j-7223-rg5m

Published

Oct 25, 2016

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2016-1000031.

EPSS Exploitation Probability

via FIRST.org ↗

32.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

1 pkg affected

☕commons-fileupload:commons-fileupload

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

Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-fileupload:commons-fileupload`	all versions	1.3.3`commons-fileupload:commons-fileupload:1.3.3`

Affected Products

1 product · 1 configurations

Application

commons fileuploadapache

≤ 1.3.2

range

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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000031 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions