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. 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-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 pinpoints whether GHSA-6rh6-x8ww-9h97 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-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.

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

GHSA-6rh6-x8ww-9h97

CRITICAL

GHSA-6rh6-x8ww-9h97 is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.grails:grails-databinding. O3 Security confirms whether GHSA-6rh6-x8ww-9h97 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Blast Radius

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
☕Maven	`org.grails:grails-databinding`	≥ 4.0.0&&< 4.1.1	4.1.1
☕Maven	`org.grails:grails-databinding`	≥ 5.0.0&&< 5.1.9	5.1.9
☕Maven	`org.grails:grails-databinding`	≥ 5.2.0&&< 5.2.1	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. 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.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 pinpoints whether GHSA-6rh6-x8ww-9h97 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-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 detects GHSA-6rh6-x8ww-9h97 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