CVE-2025-32952

io.jmix.localfs:jmix-localfs affected by DoS in the Local File Storage

Workarounds

A workaround for those who are unable to upgrade: Disable Files Endpoint in Jmix Application.

The local file storage implementation does not restrict the size of uploaded files. An attacker could exploit this by uploading excessively large files, potentially causing the server to run out of space and return HTTP 500 error, resulting in a denial of service.

The severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2025-32952 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.2, 2.4.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been fixed in Jmix 1.6.2+ and 2.4.0+.

1. What is CVE-2025-32952? CVE-2025-32952 is a medium-severity allocation of resources without limits or throttling vulnerability in io.jmix.localfs:jmix-localfs (maven), affecting versions >= 1.0.0, < 1.6.2. It is fixed in 1.6.2, 2.4.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2025-32952? CVE-2025-32952 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of io.jmix.localfs:jmix-localfs are affected by CVE-2025-32952? io.jmix.localfs:jmix-localfs (maven) versions >= 1.0.0, < 1.6.2 is affected.
4. Is there a fix for CVE-2025-32952? Yes. CVE-2025-32952 is fixed in 1.6.2, 2.4.0. Upgrade to this version or later.
5. Is CVE-2025-32952 exploitable, and should I be worried? Whether CVE-2025-32952 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32952 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32952?
   • Upgrade io.jmix.localfs:jmix-localfs to 1.6.2 or later
   • Upgrade io.jmix.localfs:jmix-localfs to 2.4.0 or later

Other vulnerabilities in io.jmix.localfs:jmix-localfs