How severe is GHSA-6rh6-x8ww-9h97?

GHSA-6rh6-x8ww-9h97 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6rh6-x8ww-9h97?

GHSA-6rh6-x8ww-9h97 affects the following packages: org.grails:grails-databinding (Maven), org.grails:grails-databinding (Maven), org.grails:grails-databinding (Maven), org.grails:grails-databinding (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6rh6-x8ww-9h97?

Update org.grails:grails-databinding to 3.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rh6-x8ww-9h97 is resolved across your whole dependency graph.

How do I detect GHSA-6rh6-x8ww-9h97 in my Maven dependencies?

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.

How do I mitigate GHSA-6rh6-x8ww-9h97 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-6rh6-x8ww-9h97?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6rh6-x8ww-9h97 can be triaged on real exposure rather than presence alone.

Is GHSA-6rh6-x8ww-9h97 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6rh6-x8ww-9h97 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-6rh6-x8ww-9h97?

GHSA-6rh6-x8ww-9h97 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 82th 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.

When was GHSA-6rh6-x8ww-9h97 published, and has it been updated?

GHSA-6rh6-x8ww-9h97 was published on July 21, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-6rh6-x8ww-9h97 — grails-databinding

CRITICAL

GHSA-6rh6-x8ww-9h97 is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.grails:grails-databinding. A fix is available for org.grails:grails-databinding — see the affected versions and patch details below.

Grails framework Remote Code Execution via Data Binding

Also known asCVE-2022-35912

Published

Jul 21, 2022

Updated

Jul 8, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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-6rh6-x8ww-9h97 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,166 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

4 pkgs affected

☕org.grails:grails-databinding☕org.grails:grails-databinding☕org.grails:grails-databinding☕org.grails:grails-databinding

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

Impact

A vulnerability has been discovered in the Grails data-binding logic which allows for Remote Code Execution in a Grails application. This exploit requires the application to be running on Java 8, either deployed as a WAR to a servlet container, or an executable JAR.

Patches

Grails framework versions 5.2.1, 5.1.9, 4.1.1, and 3.3.15

References

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35912 https://grails.org/blog/2022-07-18-rce-vulnerability.html

For more information

If you have any questions or comments about this advisory:

Credit

This vulnerability was discovered by meizjm3i and codeplutos of AntGroup FG Security Lab

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.grails:grails-databinding`	≥ 3.3.10&&< 3.3.15	3.3.15`org.grails:grails-databinding:3.3.15`
☕Maven	`org.grails:grails-databinding`	≥ 4.0.0&&< 4.1.1	4.1.1`org.grails:grails-databinding:4.1.1`
☕Maven	`org.grails:grails-databinding`	≥ 5.0.0&&< 5.1.9	5.1.9`org.grails:grails-databinding:5.1.9`
☕Maven	`org.grails:grails-databinding`	≥ 5.2.0&&< 5.2.1	5.2.1`org.grails:grails-databinding:5.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
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 3.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rh6-x8ww-9h97 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-6rh6-x8ww-9h97 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6rh6-x8ww-9h97. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A vulnerability has been discovered in the Grails data-binding logic which allows for Remote Code Execution in a Grails application. This exploit requires the application to be running on Java 8, either deployed as a WAR to a servlet container, or an executable JAR. ### Patches Grails framework versions 5.2.1, 5.1.9, 4.1.1, and 3.3.15 ### References https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35912 https://grails.org/blog/2022-07-18-rce-vulnerability.html ### For more information If you have any questions or comments about this advisory: * https://grails.org/blog/20

O3 Security · Impact-Aware SCA

Is GHSA-6rh6-x8ww-9h97 in your dependencies?

O3 Security finds GHSA-6rh6-x8ww-9h97 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works