How severe is GHSA-4gc7-5j7h-4qph?

GHSA-4gc7-5j7h-4qph has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4gc7-5j7h-4qph?

GHSA-4gc7-5j7h-4qph affects the following packages: org.springframework:spring-context (Maven), org.springframework:spring-web (Maven), org.springframework:spring-web (Maven), org.springframework:spring-context (Maven), org.springframework:spring-context (Maven), org.springframework:spring-web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-4gc7-5j7h-4qph?

Update org.springframework:spring-context to 6.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gc7-5j7h-4qph is resolved across your whole dependency graph.

How do I detect GHSA-4gc7-5j7h-4qph in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-context. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4gc7-5j7h-4qph if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4gc7-5j7h-4qph?

O3 pinpoints whether GHSA-4gc7-5j7h-4qph is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4gc7-5j7h-4qph actively exploited in the wild?

No public exploit code has been indexed for GHSA-4gc7-5j7h-4qph yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4gc7-5j7h-4qph?

GHSA-4gc7-5j7h-4qph has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4gc7-5j7h-4qph?

GHSA-4gc7-5j7h-4qph is classified as CWE-178 (CWE-178). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4gc7-5j7h-4qph published, and has it been updated?

GHSA-4gc7-5j7h-4qph was published on October 18, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-4gc7-5j7h-4qph: Spring Framework DataBinder Case Sensitive…

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk46th percentile-0.88%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

☕org.springframework:spring-context☕org.springframework:spring-web☕org.springframework:spring-web☕org.springframework:spring-context☕org.springframework:spring-context☕org.springframework:spring-web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive. However, String.toLowerCase() has some Locale dependent exceptions that could potentially result in fields not protected as expected.

Affected Packages

6 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-context`	≥ 6.1.0&&< 6.1.14	6.1.14
☕Maven	`org.springframework:spring-web`	≥ 6.1.0&&< 6.1.14	6.1.14
☕Maven	`org.springframework:spring-web`	≥ 6.0.0	No fix
☕Maven	`org.springframework:spring-context`	≥ 6.0.0	No fix
☕Maven	`org.springframework:spring-context`	all versions	No fix
☕Maven	`org.springframework:spring-web`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-context. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework:spring-context to 6.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gc7-5j7h-4qph is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4gc7-5j7h-4qph is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4gc7-5j7h-4qph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive. However, String.toLowerCase() has some Locale dependent exceptions that could potentially result in fields not protected as expected.

O3 Security · Impact-Aware SCA

Is GHSA-4gc7-5j7h-4qph in your dependencies?

O3 detects GHSA-4gc7-5j7h-4qph across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-4gc7-5j7h-4qph