Spring Framework DataBinder Case Sensitive Match Exception

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2025-22233: 0.43% estimated exploitation activity in the next 30 days; percentile 37.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 | OSS | | 6.1.x | 6.1.20 | OSS | | 6.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…

Published by the source

16 May 2025, 21:32 UTC

Last modified by the source

2 Jun 2025, 16:03 UTC

Source last checked

26 Oct 2026, 16:36 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4wp7-92pw-q264

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-22233

Advisory: Spring Framework DataBinder Case Sensitive Match Exception
IDs: CVE-2025-22233, GHSA-4wp7-92pw-q264
Record: https://patchnext.com/advisories/cve-2025-22233 (revision 1, source checked 26 Oct 2026, 16:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework:spring-context 6.2.7, 6.1.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework:spring-context: affected >= 6.2.0, <= 6.2.6; >= 6.1.0, <= 6.1.19; >= 6.0.0, <= 6.0.23; <= 5.3.39; fixed in 6.2.7, 6.1.20

## Suggested inspection (read-only)
- Maven org.springframework:spring-context: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework:spring-context.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4wp7-92pw-q264 (GitHub-reviewed advisory GHSA-4wp7-92pw-q264 lists affected ranges: Maven org.springframework:spring-context >=6.2.0 =6.1.0 =6.0.0 =0 <=5.3.39)

Commands are suggestions: review each one before running it.