# CVE-2023-26048: OutOfMemoryError for large multipart without filename in Eclipse Jetty

> Attackers can cause OutOfMemoryError and service disruption in Eclipse Jetty by sending large multipart requests without filenames.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** CLEANSTART-2026-SC99886, CLEANSTART-2026-YU71796, DEBIAN-CVE-2023-26048, GHSA-qw69-rqj8-6qw8, UBUNTU-CVE-2023-26048

## What is CVE-2023-26048?

CVE-2023-26048 is a medium-severity denial of service vulnerability in Eclipse Jetty, published on 18 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with `@MultipartConfig`) that call `HttpServletRequest.getParameter()` or `HttpServletRequest.getParts()` may cause `OutOfMemoryError` when the client sends a multipart request with a part that has a name but no filename and very large content. This happens even with the default settings of `fileSizeThreshold=0` which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throw `OutOfMemoryError`. However, the server may be able to recover after the `OutOfMemoryError` and continue its service -- although it may take some time. This issue has been patched in versions 9.4.51, 10.0.14, and 11.0.14. Users are advised to upgrade. Users unable to upgrade may set the multipart parameter `maxRequestSize` which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-26048?

6 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty:jetty-server` | Maven | All versions | 9.4.51.v20230217 |
| `org.eclipse.jetty:jetty-server` | Maven | All versions | 9.4.51.v20230217 |
| `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.14 |
| `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.14 |
| `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.14 |
| `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.14 |

Products: Eclipse Jetty.

## How do I fix CVE-2023-26048?

Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 9.4.51.v20230217, 10.0.14 or 11.0.14.

## Is CVE-2023-26048 being exploited?

There is no known exploitation of CVE-2023-26048 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Trinadh465/jetty_9.4.31_CVE-2023-26048 (github_poc): https://github.com/Trinadh465/jetty_9.4.31_CVE-2023-26048

## Other vulnerabilities in Eclipse Jetty

- [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8)
- [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4)
- [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8)
- [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7)
- [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26048 and fix it if it is affected.

What it is: CVE-2023-26048 is a medium-severity denial of service vulnerability in Eclipse Jetty, published on 18 Apr 2023. 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-2023-26048 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty:jetty-server (Maven): affected all versions; fixed in 9.4.51.v20230217
- org.eclipse.jetty:jetty-server (Maven): affected all versions; fixed in 9.4.51.v20230217
- org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.14
- org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.14
- org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.14
- org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.14

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-2023-26048/ (Markdown: https://insights.sbomify.com/CVE-2023-26048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26048
- OSV: https://osv.dev/vulnerability/CVE-2023-26048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-26048/
Summaries are generated and may contain mistakes; the official description above is the record.