Loading vulnerability…
CVE-2023-26048 is an uncontrolled resource-allocation vulnerability in Eclipse Jetty multipart servlet processing. In affected versions, a servlet configured for multipart handling, including one using @MultipartConfig, may retain multipart content in memory when it calls HttpServletRequest.getParameter() or HttpServletRequest.getParts(). A remote client can submit a multipart request containing a part with a field name, no filename, and very large content. This can trigger an OutOfMemoryError even when fileSizeThreshold is set to its default value of zero, which would ordinarily cause part content to be streamed to disk.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Jetty Server denial-of-service condition causing OutOfMemoryError when large multipart data without a filename is read using request.getParameter().
Jetty multipart request processing vulnerability that can cause an OutOfMemoryError.
A Jetty Server flaw where processing a large multipart request without a filename through request.getParameter() can cause an OutOfMemoryError.
A Jetty Server denial-of-service issue in which processing a large multipart request without a filename through request.getParameter() can cause an OutOfMemoryError.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.