io.jmix.localfs:jmix-localfs has a Path Traversal in Local 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:H/I:N/A:N

EPSS

• CVE-2025-32950: 0.73% estimated exploitation activity in the next 30 days; percentile 54.44 (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 Attackers could manipulate the FileRef parameter to access files on the system where the Jmix application is deployed, provided the application server has the necessary permissions. This can be accomplished either by modifying the FileRef directly in the database or by supplying a harmful value in the fileRef parameter of the /files endpoint of the generic REST API. Arbitrary file reading on the operating system where the Jmix process is running. 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. Workarounds A workaround for those who are unable to upgrade: Fix Path Traversal in Jmix Application. Credit Cai, Qi Qi of Siemens China Cybersecurity Testing Center - Shadowless Lab

Published by the source

22 Apr 2025, 16:50 UTC

Last modified by the source

27 May 2025, 17:07 UTC

Source last checked

26 Oct 2026, 16:36 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jx4g-3xqm-62vh

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

# Patch Next advisory brief: CVE-2025-32950

Advisory: io.jmix.localfs:jmix-localfs has a Path Traversal in Local File Storage
IDs: CVE-2025-32950, GHSA-jx4g-3xqm-62vh
Record: https://patchnext.com/advisories/cve-2025-32950 (revision 1, source checked 26 Oct 2026, 16:36 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: io.jmix.localfs:jmix-localfs 2.4.0, 1.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jmix.localfs:jmix-localfs: affected >= 1.0.0, < 1.6.2; >= 2.0.0, < 2.4.0; fixed in 2.4.0, 1.6.2

## Suggested inspection (read-only)
- Maven io.jmix.localfs:jmix-localfs: 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 io.jmix.localfs:jmix-localfs.
- 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-jx4g-3xqm-62vh (GitHub-reviewed advisory GHSA-jx4g-3xqm-62vh lists affected ranges: Maven io.jmix.localfs:jmix-localfs >=1.0.0 =2.0.0 <2.4.0)

Commands are suggestions: review each one before running it.