How severe is CVE-2025-32952?

CVE-2025-32952 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-2025-32952?

CVE-2025-32952 affects the following packages: io.jmix.localfs:jmix-localfs (Maven), io.jmix.localfs:jmix-localfs (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-32952?

Update io.jmix.localfs:jmix-localfs to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32952 is resolved across your whole dependency graph.

How do I detect CVE-2025-32952 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jmix.localfs:jmix-localfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32952 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-2025-32952 actively exploited in the wild?

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

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

CVE-2025-32952 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-32952 published, and has it been updated?

CVE-2025-32952 was published on April 22, 2025 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-2025-32952 — jmix-localfs

MEDIUMFix: jmix-framework/jmix@6a66aa3

CVE-2025-32952 is a medium-severity (CVSS 6.5) CWE-770 vulnerability in io.jmix.localfs:jmix-localfs. A fix is available for io.jmix.localfs:jmix-localfs — see the affected versions and patch details below.

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

Also known asGHSA-f3gv-cwwh-758m

Published

Apr 22, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32952.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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

2 pkgs affected

☕io.jmix.localfs:jmix-localfs☕io.jmix.localfs:jmix-localfs

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

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.

Patches

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

Workarounds

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jmix.localfs:jmix-localfs`	≥ 1.0.0&&< 1.6.2	1.6.2`io.jmix.localfs:jmix-localfs:1.6.2`
☕Maven	`io.jmix.localfs:jmix-localfs`	≥ 2.0.0&&< 2.4.0	2.4.0`io.jmix.localfs:jmix-localfs:2.4.0`

Affected Products

4 products · 5 configurations

Application

cuba platformhaulmont

≥ 6.2.0 && < 7.2.23

range

Application

cuba rest apihaulmont

≥ 7.1.1 && < 7.2.7

range

Application

jmix frameworkhaulmont

≥ 2.0.0 && < 2.4.0

range

Application

jpa web apihaulmont

≥ 1.0.0 && < 1.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jmix.localfs:jmix-localfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jmix.localfs:jmix-localfs to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32952 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 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. ### Patches The problem has been fixed in Jmix 1.6.2+ and