# CVE-2016-3092: High severity vulnerability that affects commons-fileupload:commons-fileupload > Remote attackers can cause denial of service via CPU consumption using a long boundary string in Apache Commons Fileupload. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Jul 2016 - **Updated:** 7 Oct 2026 - **Also known as:** DEBIAN-CVE-2016-3092, DLA-528-1, DLA-529-1, DSA-3611-1, DSA-3614-1, GHSA-fvm3-cfvj-gxqq, MGASA-2016-0260, RHSA-2016:2068, RHSA-2016:2069, RHSA-2016:2070, RHSA-2016:2072, UBUNTU-CVE-2016-3092, USN-3027-1 ## What is CVE-2016-3092? CVE-2016-3092 is a high-severity denial of service vulnerability in Apache Tomcat, published on 4 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2016-3092? 2 open source packages ship an affected version, including commons-fileupload:commons-fileupload. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `commons-fileupload:commons-fileupload` | Maven | All versions | 1.3.2 | | `commons-fileupload:commons-fileupload` | Maven | All versions | 1.3.2 | | `apache-cxf` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.7.18-4.SP3_redhat_1.1.ep6.el5 | | `hornetq` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.3.25-16.SP14_redhat_1.1.ep6.el5 | | `jboss-as-appclient` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-cli` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-client-all` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-clustering` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-cmp` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-connector` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-controller-client` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-core-security` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-deployment-repository` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-deployment-scanner` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-domain-http` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-domain-management` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-ee` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-ee-deployment` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-ejb3` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-embedded` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-host-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jacorb` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jaxr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jaxrs` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jdr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jmx` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jpa` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jsf` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-jsr77` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-logging` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-mail` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-management-client-content` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-messaging` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-modcluster` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-naming` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-network` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-osgi` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | | `jboss-as-osgi-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.11-1.Final_redhat_1.1.ep6.el5 | Products: Apache Commons Fileupload, Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Hp Icewall Identity Manager, Hp Icewall Sso Agent Option. ## How do I fix CVE-2016-3092? Upgrade commons-fileupload:commons-fileupload to 1.3.2 or later. ## Is CVE-2016-3092 being exploited? There is no known exploitation of CVE-2016-3092 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2016-1000031](https://insights.sbomify.com/CVE-2016-1000031/): Improper Access Control in commons-fileupload (critical 9.8) - [CVE-2025-48976](https://insights.sbomify.com/CVE-2025-48976/): Apache Commons FileUpload, Apache Commons FileUpload: FileUpload DoS via part headers (high 7.5) - [CVE-2023-24998](https://insights.sbomify.com/CVE-2023-24998/): Apache Commons FileUpload, Apache Tomcat: FileUpload DoS with excessive parts (high 7.5) - [CVE-2014-0050](https://insights.sbomify.com/CVE-2014-0050/): Commons FileUpload Denial of service vulnerability (high 7.5) - [CVE-2013-0248](https://insights.sbomify.com/CVE-2013-0248/): Incorrect Default Permissions in Apache Commons FileUpload (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-3092 and fix it if it is affected. What it is: CVE-2016-3092 is a high-severity denial of service vulnerability in Apache Tomcat, published on 4 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-3092 in the wild and no public exploit code. Affected packages and fixed versions: - commons-fileupload:commons-fileupload (Maven): affected all versions; fixed in 1.3.2 - commons-fileupload:commons-fileupload (Maven): affected all versions; fixed in 1.3.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-3092/ (Markdown: https://insights.sbomify.com/CVE-2016-3092/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-3092 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-3092 - OSV: https://osv.dev/vulnerability/CVE-2016-3092 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-3092/ Summaries are generated and may contain mistakes; the official description above is the record.