Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-3pjv-r7w4-2cf5

Grails data binding causes JVM crash and/or other denial of service

CVSS 6.5 MediumEPSS 0.0072 · 54th percentile

Published by the GitHub Advisory Database at 20 Dec 2023, 21:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.grails:grails-databindingMaven>=6.0.0, <6.1.0 || >=5.0.0, <5.3.4 || >=4.0.0, <4.1.3 || >=2.0.0, <3.3.176.1.0, 5.3.4, 4.1.3, 3.3.17
Identifiers
GHSA-3pjv-r7w4-2cf5 · CVE-2023-46131
Weakness (CWE)
CWE-400
Tags
Published
20 Dec 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The org.grails:grails-databinding package is vulnerable across several version ranges, including 2.0.0 up to 3.3.17, 4.0.0 up to 4.1.3, 5.0.0 up to 5.3.4, and 6.0.0 up to 6.1.0. A specially crafted web request can crash the JVM or cause a denial of service in any Grails application that uses data binding, and the source does not describe further conditions. Upgrade to 6.1.0, 5.3.4, 4.1.3, or 3.3.17, depending on your release line. The only workaround listed is to avoid binding data from request input.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0072, the 54th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.