GHSA-3pjv-r7w4-2cf5 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.grails:grails-databinding. A fix is available for org.grails:grails-databinding — see the affected versions and patch details below.
Grails data binding causes JVM crash and/or other denial of service
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-3pjv-r7w4-2cf5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.grails:grails-databinding☕org.grails:grails-databinding☕org.grails:grails-databinding☕org.grails:grails-databindingReal-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
Impact
A specially crafted web request can lead to a JVM crash or denial of service. Any Grails framework application using Grails data binding is vulnerable.
Patches
Patches are available for Grails 3 and later.
Workarounds
No workaround is possible except to avoid data binding to request data.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.grails:grails-databinding | ≥ 6.0.0&&< 6.1.0 | 6.1.0org.grails:grails-databinding:6.1.0 |
| ☕Maven | org.grails:grails-databinding | ≥ 5.0.0&&< 5.3.4 | 5.3.4org.grails:grails-databinding:5.3.4 |
| ☕Maven | org.grails:grails-databinding | ≥ 4.0.0&&< 4.1.3 | 4.1.3org.grails:grails-databinding:4.1.3 |
| ☕Maven | org.grails:grails-databinding | ≥ 2.0.0&&< 3.3.17 | 3.3.17org.grails:grails-databinding:3.3.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.grails:grails-databinding, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.grails:grails-databinding to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pjv-r7w4-2cf5 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3pjv-r7w4-2cf5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3pjv-r7w4-2cf5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3pjv-r7w4-2cf5 in your dependencies?
O3 Security finds GHSA-3pjv-r7w4-2cf5 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.