CVE-2026-47885

Spring Framework maxPartSize Ignored in PartEventHttpMessageReader

Published Aug 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
The PartEventHttpMessageReader in Spring WebFlux does not enforce the maxPartSize limit when maxInMemorySize is set to -1.
Spring Framework 7.0.0 - 7.0.8
Spring Framework 6.2.0 - 6.2.19
Spring Framework 6.1.0 - 6.1.28

Analysis

AI-generated

Technical impact

The PartEventHttpMessageReader in Spring WebFlux does not enforce the configured maxPartSize when maxInMemorySize is set to –1. This oversight allows an attacker to submit multipart requests containing parts that far exceed the intended memory limit, potentially exhausting server memory and causing the application to slow down or crash. The result is a denial‑of‑service condition that can impact the availability of services built on affected Spring Framework versions. The likely attack vector is sending oversized multipart requests over the network, based on the description.

Affected Systems

Spring Framework versions 7.0.0 through 7.0.8, 6.2.0 through 6.2.19, and 6.1.0 through 6.1.28 are affected. These releases are provided by Spring and represent the only publicly documented affected releases.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity. The EPSS score of <1% indicates a low but nonzero probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, the flaw does not require authentication; it is inferred that an attacker can exploit it over the network by sending specially crafted large multipart HTTP requests. Since the issue depends on the application accepting multipart payloads with maxInMemorySize set to –1, it is inferred that exploitation is straightforward when such a configuration is in place.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Reconfigure Spring to avoid setting maxInMemorySize to –1, enabling enforcement of maxPartSize to mitigate resource exhaustion and input validation issues.
  • Implement custom middleware or request filters that validate multipart payload sizes and enforce memory limits until an official vendor fix is released.
  • Review Spring Framework documentation and official security advisories regularly to apply any updates that address this issue.

Generated by OpenCVE AI on August 28, 2026 at 07:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Framework
CPEs cpe:2.3:a:vmware:spring_framework:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Framework
Type Values Removed Values Added
Weaknesses CWE-689
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Framework
Vendors & Products Spring
Spring spring Framework
Type Values Removed Values Added
Weaknesses CWE-689
CWE-770
Type Values Removed Values Added
Description The PartEventHttpMessageReader in Spring WebFlux does not enforce the maxPartSize limit when maxInMemorySize is set to -1. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28
Title Spring Framework maxPartSize Ignored in PartEventHttpMessageReader
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 27, 2026, 3:01 PM
Reserved
May 20, 2026, 10:01 AM
Status
Undergoing Analysis
Published
Aug 27, 2026, 6:17 AM
Modified
Sep 10, 2026, 2:06 PM