PatchSiren cyber security CVE debrief
CVE-2026-47885 Spring CVE debrief
CVE-2026-47885 PartEventHttpMessageReader Security Vulnerability in Spring WebFlux allows potential denial-of-service (DoS) attacks and data tampering due to improper size limits. Defenders should assess exposure and prioritize patching for Spring Framework versions 6.1.0 through 6.1.28, 6.2.0 through 6.2.19, and 7.0.0 through 7.0.8. This executive overview covers the affected product, vulnerability class, likely operational impact, and source-confidence limits, emphasizing the need for configuration reviews and mitigation strategies.
- Vendor
- Spring
- Product
- Spring Framework
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-27
- Original CVE updated
- 2026-09-10
- Advisory published
- 2026-08-27
- Advisory updated
- 2026-09-10
Who should care
Defenders responsible for Spring Framework deployments, vulnerability management teams, and security operators should assess exposure and prioritize patching. They should review configurations, verify patch application, and monitor for potential exploitation attempts. This includes teams managing Spring-based applications, security teams responsible for vulnerability management, and operators handling system updates.
Why it matters
CVE-2026-47885 is a high-severity vulnerability in Spring Framework's PartEventHttpMessageReader. Defenders should prioritize patching and configuration reviews to mitigate potential DoS attacks and data tampering risks.
- Potential denial-of-service (DoS) attacks
- Data tampering or corruption due to improper size limits
- Increased risk of successful exploitation due to default configurations
- Verification of patch application and configuration updates
Technical summary
The PartEventHttpMessageReader in Spring WebFlux does not enforce the maxPartSize limit when maxInMemorySize is set to -1. This affects Spring Framework versions 6.1.0 through 6.1.28, 6.2.0 through 6.2.19, and 7.0.0 through 7.0.8. The vulnerability allows potential denial-of-service (DoS) attacks and data tampering or corruption due to improper size limits. Defenders should prioritize verifying and applying patches, reviewing and updating maxPartSize and maxInMemorySize configurations, and monitoring for potential exploitation attempts.
Defensive priority
Defenders should prioritize verifying and applying patches for Spring Framework versions 6.1.0 through 6.1.28, 6.2.0 through 6.2.19, and 7.0.0 through 7.0.8.
Recommended defensive actions
- Verify and apply patches for affected Spring Framework versions
- Review and update maxPartSize and maxInMemorySize configurations
- Monitor for potential exploitation attempts
Evidence notes
The CVE record and NVD entry provide details on the PartEventHttpMessageReader vulnerability in Spring WebFlux, which does not enforce the maxPartSize limit when maxInMemorySize is set to -1.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-47885 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-47885
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-47885 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47885
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://spring.io/security/cve-2026-47885
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.