Spring Framework DataBinder Case Sensitive Match Exception

published 2025-05-16 17 mo ago modified 2026-09-10 1 mo ago also GHSA-4wp7-92pw-q264 , EUVD-2025-15542

cvss: 3.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks.

Affected Spring Products and Versions

Spring Framework: * 6.2.0 - 6.2.6

* 6.1.0 - 6.1.19

* 6.0.0 - 6.0.27

* 5.3.0 - 5.3.42 * Older, unsupported versions are also affected

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.

Affected version(s)Fix Version Availability 6.2.x 6.2.7 OSS6.1.x 6.1.20 OSS6.0.x 6.0.28 Commercial https://enterprise.spring.io/ 5.3.x 5.3.43 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary.

Generally, we recommend using a dedicated model object with properties only for data binding, or using constructor binding since constructor arguments explicitly declare what to bind together with turning off setter binding through the declarativeBinding flag. See the Model Design section in the reference documentation.

For setting binding, prefer the use of allowedFields (an explicit list) over disallowedFields.

Credit

This issue was responsibly reported by the TERASOLUNA Framework Development Team from NTT DATA Group Corporation.

Patch / fix

fixed in 2 links 2

maven org.springframework:spring-context 6.1.20, 6.2.7
Spring Spring Framework 5.3.43, 6.0.28, 6.1.20, 6.2.7

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 17 mo ago (2025-05-17)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub	3.1	3.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.springframework:spring-context	>=6.2.0, <6.2.7 >=6.1.0, <6.1.20 >=6.0.0, <=6.0.23 <=5.3.39	6.2.7 6.1.20

Affected products

Spring Spring Framework

Classification

Weakness

CWE-20 Improper Input Validation

Technology feeds

Spring rss critical rss

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary