CVE Tools

CVE-2025-48976

Apache Commons FileUpload, Apache Commons FileUpload: FileUpload DoS via part headers

Exploitation likely. EPSS gives it a 33% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, GitHub, BDU, CSAF

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Ask IT to check whether any application uses Apache Commons FileUpload and identify its installed version.
  2. Upgrade the 1.x package to 1.6.0 or later.
  3. Upgrade the 2.x core package to 2.0.0-M4 or later.
  4. Until updated, restrict public file-upload endpoints and enforce request-size limits at the web server or gateway.

What it is

From the CVE record

Allocation of resources for multipart headers with insufficient limits enabled a DoS vulnerability in Apache Commons FileUpload. This issue affects Apache Commons FileUpload: from 1.0 before 1.6; from 2.0.0-M1 before 2.0.0-M4. Users are recommended to upgrade to versions 1.6 or 2.0.0-M4, which fix the issue.

In plain language

Written by AI from the record

Apache Commons FileUpload versions before 1.6, and FileUpload 2.0.0-M1 through 2.0.0-M3, can be crashed by oversized upload metadata, so small businesses using it should schedule an update soon.

Unauthenticated network DoS caused by insufficient resource limits when parsing multipart part headers (CWE-770).

If you're affected

  • Website upload outages
  • Application slowdown or crash
  • Interrupted customer submissions
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS98th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

33% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 459 days, from the signal feeds we watch.

  1. EPSS band changehigh → moderateepss band change
  2. OpenVAS check added
  3. EPSS band changelow → high
  4. Patch availablerecord updated
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache Commons…, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store