CVE-2025-22233 Spring Framework DataBinder Case Sensitive Match Exception
Attackers can bypass disallowedFields checks in Spring Framework DataBinder to modify protected object properties, requiring an upgrade to fixed versions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-22233?
CVE-2025-22233 is a low-severity missing authorization vulnerability in Spring Framework, published on 16 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-20
Which versions are affected by CVE-2025-22233?
8 open source packages ship an affected version, including org.springframework:spring-context.
| Package | Affected | Fixed in |
|---|---|---|
org.springframework:spring-context Maven | All versions to 5.3.39 | None |
org.springframework:spring-context Maven | All versions to 5.3.39 | None |
org.springframework:spring-context Maven | From 6.0.0 to 6.0.23 | None |
org.springframework:spring-context Maven | From 6.0.0 to 6.0.23 | None |
org.springframework:spring-context Maven | From 6.1.0 | 6.1.20 |
org.springframework:spring-context Maven | From 6.1.0 | 6.1.20 |
2 more packages
org.springframework:spring-context Maven | From 6.2.0 | 6.2.7 |
org.springframework:spring-context Maven | From 6.2.0 | 6.2.7 |
How do I fix CVE-2025-22233?
Upgrade org.springframework:spring-context to a fixed version for your release line: 6.1.20 or 6.2.7.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2025-22233 being exploited?
There is no known exploitation of CVE-2025-22233 in the wild and no public exploit code.
Sources
Also known as CLEANSTART-2026-NT49717, CLEANSTART-2026-UT02343, CLSA-2025-1752537764, CLSA-2026-1793094381, DEBIAN-CVE-2025-22233, ECHO-e634-10ea-902d and 9 more.