Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.3% (FIRST EPSS); higher than 88.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: jetty9 (Debian:10) 9.4.16-0+deb10u3; jetty9 (Debian:11) 9.4.39-3+deb11u2; jetty9 (Debian:12) 9.4.50-4+deb12u1.

Low priority for now. Upgrade to jetty9 (Debian:10) 9.4.16-0+deb10u3; jetty9 (Debian:11) 9.4.39-3+deb11u2; jetty9 (Debian:12) 9.4.50-4+deb12u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.3 · v3.1—Proof of concept Fix available
Published
Apr 18, 2023
Updated
Jun 17, 2026
EPSS
3.3% · 88th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.3
CNA · GitHub_M
5.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-26048

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
eclipsejetty

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • eclipse jettybefore 9.4.51
  • eclipse jetty10.0.0 and later · before 10.0.14
  • eclipse jetty11.0.0 and later · before 11.0.14

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • eclipse jetty.project

    • < 9.4.51, >= 10.0.0, < 10.0.14, >= 11.0.0, < 11.0.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10jetty9before 9.4.16-0+deb10u39.4.16-0+deb10u3
Debian:11jetty9before 9.4.39-3+deb11u29.4.39-3+deb11u2
Debian:12jetty9before 9.4.50-4+deb12u19.4.50-4+deb12u1
Debian:13jetty9before 9.4.52-19.4.52-1
Mavenorg.eclipse.jetty:jetty-serverfrom 10.0.0 · before 10.0.1410.0.14
Mavenorg.eclipse.jetty:jetty-serverfrom 11.0.0 · before 11.0.1411.0.14
Mavenorg.eclipse.jetty:jetty-serverbefore 9.4.51.v202302179.4.51.v20230217
openSUSE:Leap 15.4jetty-minimalbefore 9.4.51-150200.3.19.29.4.51-150200.3.19.2
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemisbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-clibefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-commonsbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-core-clientbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-dtobefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-hornetq-protocolbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-hqclient-protocolbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-jdbc-storebefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-jms-clientbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-jms-serverbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-journalbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-rabefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-selectorbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-serverbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-service-extensionsbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap
Red Hat:jboss_enterprise_application_platform:7.4::el7eap7-activemq-artemis-toolsbefore 0:2.16.0-17.redhat_00051.1.el7eap0:2.16.0-17.redhat_00051.1.el7eap

+96

Other highest-scoring records for the same primary product.

  • CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con
    60This week
  • CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm
    60This week
  • CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem
    53Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-2048Jul 7, 2022 · In Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up no
    31Monitor
  • ← EarlierCVE-2022-2191Jul 7, 2022 · In Eclipse Jetty versions 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, SslConnection does not release ByteBuffers from configured By
    31Monitor
  • Later →CVE-2023-26049Apr 18, 2023 · Cookie parsing of quoted values can exfiltrate values from other cookies in Eclipse Jetty
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:jetty99.4.50-4+deb12u1 · Debian:12Package registry (OSV)
Maven:org.eclipse.jetty:jetty-server10.0.14Package registry (OSV)
Maven:org.eclipse.jetty:jetty-server11.0.14Package registry (OSV)
Maven:org.eclipse.jetty:jetty-server9.4.51.v20230217Package registry (OSV)
opensuse:jetty-minimal9.4.51-150200.3.19.2 · openSUSE:Leap 15.4Package registry (OSV)
red hat:eap7-activemq-artemis0:2.16.0-17.redhat_00051.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-activemq-artemis-cli0:2.16.0-17.redhat_00051.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-activemq-artemis-commons0:2.16.0-17.redhat_00051.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-guava0:32.1.1-2.jre_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-guava-libraries0:32.1.1-2.jre_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-jboss-xnio-base0:3.8.11-1.SP1_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-undertow0:2.2.28-1.SP1_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-wildfly0:7.4.14-5.GA_redhat_00002.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-wildfly-java-jdk110:7.4.14-5.GA_redhat_00002.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-wildfly-java-jdk80:7.4.14-5.GA_redhat_00002.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-wildfly-javadocs0:7.4.14-5.GA_redhat_00002.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-wildfly-modules0:7.4.14-5.GA_redhat_00002.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
suse:jetty-minimal9.4.51-150200.3.19.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02023-11-01

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+196 d
  3. TodayNov 6, 2026+1297 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

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

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records