CVE-2026-47891

Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder

Published Aug 27, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit.
Spring Framework 7.0.0 - 7.0.8
Spring Framework 6.2.0 - 6.2.19
Spring Framework 6.1.0 - 6.1.28
Spring Framework 6.0.0 - 6.0.30
Spring Framework 5.3.0 - 5.3.49
Spring Framework 5.2.25.RELEASE and earlier

Analysis

AI-generated

Technical impact

A Spring WebFlux application that uses the Aalto XML processor does not enforce the configured maxInMemorySize limit, allowing an attacker to send oversized XML payloads that bypass the restriction and consume unlimited memory, ultimately leading to application failure or unresponsiveness. The failure to constrain resource consumption results in a denial‑of‑service impact on availability, and if the crash exposes stack traces or other diagnostic data, there is a potential for confidentiality loss. The weakness relates to improper resource limit enforcement (CWE‑400) and uncontrolled memory growth (CWE‑770).

Affected Systems

Spring Framework versions 7.0.0 through 7.0.8, 6.2.0 through 6.2.19, 6.1.0 through 6.1.28, 6.0.0 through 6.0.30, 5.3.0 through 5.3.49, and all 5.2.25.RELEASE versions and earlier are affected.

Risk and Exploitability

While the EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog, the lack of a memory size limit in these widely used framework versions suggests a high exploitation likelihood in environments where XML input is accepted, such as REST APIs over HTTP. The CVSS score of 9.8 indicates an extremely high severity, reinforcing the potential for significant impact if exploited. An attacker could likely exploit the flaw by sending a large XML document to any vulnerable WebFlux endpoint, forcing the application to allocate memory beyond safe limits. The resulting denial‑of‑service can be catastrophic for services that require high availability. Consequently, the overall risk is considered elevated until mitigated.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Spring Framework release that includes the fix (7.0.9 or later);
  • If an upgrade is infeasible, configure a stricter maxInMemorySize and validate incoming XML payload sizes before they reach the decoder;
  • Deploy application containers with memory limits and enable monitoring for sudden spikes to prevent full service outages.

Generated by OpenCVE AI on August 27, 2026 at 17:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
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-770
Metrics cvssV3_1

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

ssvc

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

Type Values Removed Values Added
First Time appeared Spring
Spring spring Framework
Weaknesses CWE-400
Vendors & Products Spring
Spring spring Framework
Type Values Removed Values Added
Description A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.25.RELEASE and earlier
Title Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder
References
Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 27, 2026, 2:52 PM
Reserved
May 20, 2026, 10:01 AM
Status
Analyzed
Published
Aug 27, 2026, 6:17 AM
Modified
Sep 2, 2026, 5:36 PM
Severity
Important
Public date
Aug 27, 2026, 5:21 AM