How severe is CVE-2023-26048?

CVE-2023-26048 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-26048?

CVE-2023-26048 affects the following packages: org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-26048?

Update org.eclipse.jetty:jetty-server to 9.4.51.v20230217 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26048 is resolved across your whole dependency graph.

How do I detect CVE-2023-26048 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-26048 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2023-26048 actively exploited in the wild?

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

CVE-2023-26048 has an EPSS (Exploit Prediction Scoring System) score of 3.4%, placing it in the 89th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-26048?

CVE-2023-26048 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-26048 published, and has it been updated?

CVE-2023-26048 was published on April 18, 2023 and was last updated on October 28, 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

MEDIUM severity

CVE-2023-26048 — jetty-server

MEDIUMFix: eclipse/jetty.project#9344

CVE-2023-26048 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty:jetty-server. A fix is available for org.eclipse.jetty:jetty-server — see the affected versions and patch details below.

OutOfMemoryError for large multipart without filename in Eclipse Jetty

Also known asGHSA-qw69-rqj8-6qw8

Published

Apr 18, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 3, 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.
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-2023-26048.

EPSS Exploitation Probability

via FIRST.org ↗

3.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% 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

3 pkgs affected

☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server

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

Impact

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 a 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.

A very large number of parts may cause the same problem.

Patches

Patched in Jetty versions

9.4.51.v20230217 - via PR #9345
10.0.14 - via PR #9344
11.0.14 - via PR #9344

Workarounds

Multipart parameter maxRequestSize must be set to a non-negative value, so the whole multipart content is limited (although still read into memory). Limiting multipart parameter maxFileSize won't be enough because an attacker can send a large number of parts that summed up will cause memory issues.

References

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	all versions	9.4.51.v20230217`org.eclipse.jetty:jetty-server:9.4.51.v20230217`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 10.0.0&&< 10.0.14	10.0.14`org.eclipse.jetty:jetty-server:10.0.14`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 11.0.0&&< 11.0.14	11.0.14`org.eclipse.jetty:jetty-server:11.0.14`

Affected Products

1 product · 3 configurations

Application

jettyeclipse

≥ 11.0.0 && < 11.0.14

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-server to 9.4.51.v20230217 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26048 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.426.3.1706515686-3.el8`	RHSA-2024:0778
Red Hat AMQ Streams 2.5.0	see advisory	RHSA-2023:5165
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-activemq-artemis-0:2.16.0-17.redhat_00051.1.el8eap`	RHSA-2023:7638
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9	`eap7-activemq-artemis-0:2.16.0-17.redhat_00051.1.el9eap`	RHSA-2023:7639
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-activemq-artemis-0:2.16.0-17.redhat_00051.1.el7eap`	RHSA-2023:7637
Red Hat JBoss Enterprise Application Platform Expansion Pack	`jetty-server`	RHSA-2024:3385
Red Hat Single Sign-On 7	`jetty-server`	RHSA-2024:0804
Red Hat Single Sign-On 7.6 for RHEL 7	`rh-sso7-keycloak-0:18.0.12-1.redhat_00001.1.el7sso`	RHSA-2024:0798

Frequently Asked Questions

### Impact 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 a 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 `OutOfMemoryEr