Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Denial of Service in Spring WebFlux Multipart Request Processing

IdentifiersCVE-2026-41840CWE-400· Uncontrolled Resource Consumption

CVE-2026-41840 is a denial-of-service vulnerability in Spring Framework affecting Spring WebFlux applications that process multipart requests. The issue is described as a multipart parsing flaw in the WebFlux request-processing path whereby crafted malicious multipart requests can trigger memory leakage during request handling. This can progressively exhaust application memory and destabilize the host or application runtime. Affected versions are Spring Framework 7.0.0 through 7.0.7, 6.2.0 through 6.2.18, 6.1.0 through 6.1.27, and 5.3.0 through 5.3.48; unsupported versions are also reported as affected.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to degrade availability by causing memory leaks and resource exhaustion in vulnerable Spring WebFlux applications. Repeated or sustained malicious multipart requests can consume sufficient memory to impair service responsiveness or crash the application, resulting in denial of service. The provided CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates the impact is limited to availability, with no stated confidentiality or integrity impact.

Mitigation

If you can’t patch tonight, do this now.

The provided content states that no further mitigation steps are necessary beyond upgrading. If immediate patching is not possible, the information provided does not specify an official workaround or compensating control.

Remediation

Patch, then assume compromise.

Upgrade Spring Framework to a fixed release. The content identifies the following fixed versions: 7.0.8 for 7.0.x OSS users, 6.2.19 for 6.2.x OSS users, 7.0.7.1 as a commercial fix for 7.0.x, 6.2.18.1 as a commercial fix for 6.2.x, 6.1.28 as the commercial fix for 6.1.x, and 5.3.49 as the commercial fix for 5.3.x. Users on unsupported branches should migrate to a supported fixed version. The content also recommends validating the upgrade with regression testing.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BroadcomSpring Frameworkapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.