CVE Watchtower

CVE-2026-59393Spring Framework Allocation of Resources Without Limits or Throttling

Spring

Vulnerability Summary

Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder. Spring Framework's WebFlux XML decoding can exceed the configured maxInMemorySize limit. This is a follow-up to CVE-2026-47891. An application is affected if it decodes XML request or response bodies with WebFlux using the Aalto XML parser. In that case, a specially crafted XML payload can cause memory consumption to grow beyond the configured limit, potentially leading to denial of service.
Severity Level
MEDIUM(4.3)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The product allocates a reusable resource on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated.
CVSS v3.1 Base Metrics — Score 4.3 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityLow

Affected & Patched Versions

Affected Versions
  • Spring Framework 7.0.0 through 7.0.10
  • Spring Framework 6.2.0 through 6.2.20
  • Spring Framework 6.1.0 through 6.1.29
  • Spring Framework 6.0.0 through 6.0.32
  • Spring Framework 5.3.0 through 5.3.50
  • Spring Framework through 5.2.26.RELEASE
Patched Versions
  • Spring Framework 7.0.11 (open source)
  • Spring Framework 7.0.10.1 (commercial support only)
  • Spring Framework 6.2.21 (commercial support only)
  • Spring Framework 6.1.30 (commercial support only)
  • Spring Framework 6.0.33 (commercial support only)
  • Spring Framework 5.3.51 (commercial support only)
  • Spring Framework 5.2.27.RELEASE (commercial support only)

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Spring Framework and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring Framework CVEsYou are reading CVE-2026-59393. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Framework CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC