How severe is CVE-2023-46131?

CVE-2023-46131 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-46131?

CVE-2023-46131 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 CVE-2023-46131?

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 CVE-2023-46131 is resolved across your whole dependency graph.

How do I detect CVE-2023-46131 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 CVE-2023-46131 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2023-46131 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-46131 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 CVE-2023-46131?

CVE-2023-46131 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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 CVE-2023-46131?

CVE-2023-46131 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-46131 published, and has it been updated?

CVE-2023-46131 was published on December 20, 2023 and was last updated on October 28, 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

MEDIUM severity

CVE-2023-46131 — grails-databinding

MEDIUMFix: grails/grails-core@74326bd

CVE-2023-46131 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 DoS

Also known asGHSA-3pjv-r7w4-2cf5

Published

Dec 20, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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 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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.grails:grails-databinding`	≥ 6.0.0&&< 6.1.0	6.1.0`org.grails:grails-databinding:6.1.0`
☕Maven	`org.grails:grails-databinding`	≥ 5.0.0&&< 5.3.4	5.3.4`org.grails:grails-databinding:5.3.4`
☕Maven	`org.grails:grails-databinding`	≥ 4.0.0&&< 4.1.3	4.1.3`org.grails:grails-databinding:4.1.3`
☕Maven	`org.grails:grails-databinding`	≥ 2.0.0&&< 3.3.17	3.3.17`org.grails:grails-databinding:3.3.17`

Affected Products

1 product · 4 configurations

Application

grailsgrails

≥ 6.0.0 && < 6.1.0

range

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 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46131 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### 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 - [Blog post](https://grails.org/blog/2023-12-20-cve-data-binding-dos.html) - [Discussion](https://github.com/grails/grails-core/issues/13302) - [Mitre CVD record](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46131)