Description
Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack.
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
Published: 2026-08-27
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Spring Framework applications that use the data binding infrastructure can be tricked into creating an unbounded list of objects when an attacker supplies a specially crafted property path. The framework repeatedly creates intermediate objects, causing memory to grow without bound. This flaw allows an attacker to exhaust server resources, resulting in a denial of service of the affected application. The weakness is an uncontrolled resource consumption flaw, rated with CWE-400.

Affected Systems

The vulnerability affects all releases of Spring Framework from 5.2.25.RELEASE and earlier up through 5.3.49, 6.0.0 to 6.0.30, 6.1.0 to 6.1.28, 6.2.0 to 6.2.19, and 7.0.0 to 7.0.8. Any application that employs Spring’s data binding to apply user‑supplied property paths is at risk. The vendor identified in the CNA is Spring:Spring Framework.

Risk and Exploitability

The CVE does not provide a CVSS score or an EPSS estimate, and it is not listed in the CISA KEV catalog. Inferred from the description, the attack vector is likely via standard HTTP requests that deliver a malicious property path to an endpoint using data binding. Because the flaw causes uncontrolled memory allocation, the potential impact is high for applications that process many such requests and lack resource limits. No exploitation evidence is cited, but the nature of the flaw suggests it could be leveraged to degrade availability if an attacker can generate large numbers of property paths.

Generated by OpenCVE AI on August 28, 2026 at 06:59 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Spring Framework to a fixed release (≥5.2.26.RELEASE, ≥5.3.50, ≥6.0.31, ≥6.1.29, ≥6.2.20, or ≥7.0.9).
  • If an upgrade cannot be performed immediately, configure @InitBinder or similar mechanisms to restrict or disable automatic property path processing on critical endpoints, limiting property depth or whitelisting acceptable paths.
  • Add application‑level request validation or size limits and monitor logs for unusually large property paths to mitigate excessive memory consumption.

Generated by OpenCVE AI on August 28, 2026 at 06:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

References
History

Fri, 28 Aug 2026 07:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400

Fri, 28 Aug 2026 06:45:00 +0000

Type Values Removed Values Added
First Time appeared Spring
Spring spring Framework
Vendors & Products Spring
Spring spring Framework

Thu, 27 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
Description Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack. 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 Denial of Service via Unbounded List Growth in Data Binding
References

Subscriptions

Spring Spring Framework
cve-icon MITRE

Status: PUBLISHED

Assigner: vmware

Published:

Updated: 2026-08-27T17:57:38.575Z

Reserved: 2026-07-04T18:13:26.297Z

Link: CVE-2026-59282

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-27T20:17:54.370

Modified: 2026-08-27T20:17:54.370

Link: CVE-2026-59282

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-28T07:00:12Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption