CVE-2025-22233

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.

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2025-22233 has a CVSS score of 3.1 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.2.7, 6.1.20); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-22233? CVE-2025-22233 is a low-severity improper input validation vulnerability in org.springframework:spring-context (maven), affecting versions >= 6.2.0, <= 6.2.6. It is fixed in 6.2.7, 6.1.20. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2025-22233? CVE-2025-22233 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.springframework:spring-context are affected by CVE-2025-22233? org.springframework:spring-context (maven) versions >= 6.2.0, <= 6.2.6 is affected.
4. Is there a fix for CVE-2025-22233? Yes. CVE-2025-22233 is fixed in 6.2.7, 6.1.20. Upgrade to this version or later.
5. Is CVE-2025-22233 exploitable, and should I be worried? Whether CVE-2025-22233 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-22233 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-22233?
   • Upgrade org.springframework:spring-context to 6.2.7 or later
   • Upgrade org.springframework:spring-context to 6.1.20 or later

Other vulnerabilities in org.springframework:spring-context