CVE-2025-48976: Apache Commons FileUpload, Apache Commons FileUpload: FileUpload DoS via part headers

Quick answers

Is CVE-2025-48976 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-48976 being exploited in the wild.

How severe is CVE-2025-48976?

Medium severity, with a CVSS score of 4, published 16 June 2025.

Which products and versions are affected?

commons-fileupload:commons-fileupload (Maven) ECOSYSTEM:introduced=1.0,fixed=1.6.0; org.apache.commons:commons-fileupload2-core (Maven) ECOSYSTEM:introduced=2.0.0-M1,fixed=2.0.0-M4.

Is there a fix for CVE-2025-48976?

Yes. commons-fileupload:commons-fileupload (Maven): upgrade to 1.6.0 or later; org.apache.commons:commons-fileupload2-core (Maven): upgrade to 2.0.0-M4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-48976?

Check whether you run commons-fileupload:commons-fileupload (Maven) or org.apache.commons:commons-fileupload2-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• commons-fileupload:commons-fileupload (Maven): upgrade to 1.6.0 or later

  # set commons-fileupload:commons-fileupload to 1.6.0 in your pom.xml or build.gradle

• org.apache.commons:commons-fileupload2-core (Maven): upgrade to 2.0.0-M4 or later

  # set org.apache.commons:commons-fileupload2-core to 2.0.0-M4 in your pom.xml or build.gradle

Affected products

• commons-fileupload:commons-fileupload (Maven) ECOSYSTEM:introduced=1.0,fixed=1.6.0
• org.apache.commons:commons-fileupload2-core (Maven) ECOSYSTEM:introduced=2.0.0-M1,fixed=2.0.0-M4

Identifiers

• CVE-2025-48976
• GHSA-vv7r-c36w-3prj