CVE-2026-59374Spring Framework Incorrect Behavior Order: Validate Before Canonicalize
Spring
Vulnerability Summary
Spring Framework Data Binding vulnerability on indexed data types. Spring Framework applications that use DataBinder's allowedFields/disallowedFields mechanism to restrict which properties may be set through data binding may be vulnerable to a data binding rules bypass when targeting indexed data types. Specifically, an application is vulnerable when all the following conditions are met: The application uses Spring's data binding infrastructure to bind user-supplied request parameters onto a target object. The application configures an exact disallowedFields pattern (or a restrictive allowedFields pattern) to exclude one or more nested, map-keyed, or list-indexed properties from binding. The application does not configure any wildcard disallowedFields pattern, or no stricter allowedFields pattern. When all conditions are met, an attacker can submit malicious form fields that will write data on fields that are explicitly excluded from data binding by the application configuration.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityHigh
AvailabilityNone
Affected & Patched 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
- 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
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Spring Framework and which version.
- 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-59374. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
More Spring Framework CVEs
External References
- Vendor Advisoryhttps://spring.io/security/cve-2026-59374
Data last checked: Nov 20, 2026 05:01 UTC