VYPR
Medium severity5.9NVD Advisory· Published Jun 9, 2026

CVE-2026-41840

CVE-2026-41840

Description

Spring WebFlux applications are vulnerable to Denial of Service (DoS) attacks via crafted multipart requests, leading to memory leaks.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Spring WebFlux applications are vulnerable to Denial of Service (DoS) attacks via crafted multipart requests, leading to memory leaks.

Vulnerability

Spring WebFlux applications are vulnerable to Denial of Service (DoS) attacks when processing multipart requests. This vulnerability affects Spring Framework versions 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. The vulnerability is present when an application uses Spring WebFlux and implements a web endpoint that receives multipart requests [1].

Exploitation

An attacker can exploit this vulnerability by sending malicious multipart requests to a vulnerable Spring WebFlux application. No specific authentication or user interaction is mentioned as required, but the attack vector involves network access to the web endpoint processing these requests [1].

Impact

Successful exploitation of this vulnerability can lead to memory leaks within the application. This can potentially result in a Denial of Service (DoS) condition, making the application unavailable to legitimate users [1].

Mitigation

Users of affected versions should upgrade to the following fixed versions: Spring Framework 7.0.8, 6.2.19, 6.1.28, and 5.3.49. No further mitigation steps are necessary beyond upgrading [1].

AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1
  • Range: 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.