Skip to content
Fencer Intel
critical 9.8

CVE-2022-35912 json

Grails framework Remote Code Execution via Data Binding

published 4y ago modified 4mo ago also GHSA-6rh6-x8ww-9h97 , EUVD-2022-6263

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

In grails-databinding in Grails before 3.3.15, 4.x before 4.1.1, 5.x before 5.1.9, and 5.2.x before 5.2.1 (at least when certain Java 8 configurations are used), data binding allows a remote attacker to execute code by gaining access to the class loader.

Patch / fix

  • maven org.grails:grails-databinding 3.3.15, 4.1.1, 5.1.9, 5.2.1
  • grails grails 3.3.15, 4.1.1, 5.1.9

Is CVE-2022-35912 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.grails:grails-databinding
>=3.3.10, <3.3.15
>=4.0.0, <4.1.1
>=5.0.0, <5.1.9
>=5.2.0, <5.2.1
3.3.15
4.1.1
5.1.9
5.2.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.