Cuba has a DoS in the File Storage

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2025-32959: 0.54% estimated exploitation activity in the next 30 days; percentile 45.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Patches The problem has been fixed in CUBA 7.2.23. Workarounds A workaround for those who are unable to upgrade: Disable Files Endpoint in CUBA Application. References Files Functionality Vulnerabilities :: Jmix Documentation Similar vulnerability in Jmix: DoS in the Local File Storage · Advisory · jmix-framework/jmix

Published by the source

22 Apr 2025, 16:57 UTC

Last modified by the source

23 Apr 2025, 15:21 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w3mp-6vrj-875g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-32959

Advisory: Cuba has a DoS in the File Storage
IDs: CVE-2025-32959, GHSA-w3mp-6vrj-875g
Record: https://patchnext.com/advisories/cve-2025-32959 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.haulmont.cuba:cuba-core 7.2.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.haulmont.cuba:cuba-core: affected < 7.2.23; fixed in 7.2.23

## Suggested inspection (read-only)
- Maven com.haulmont.cuba:cuba-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.haulmont.cuba:cuba-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w3mp-6vrj-875g (GitHub-reviewed advisory GHSA-w3mp-6vrj-875g lists affected ranges: Maven com.haulmont.cuba:cuba-core >=0 <7.2.23)

Commands are suggestions: review each one before running it.