# CVE-2025-32950: io.jmix.localfs:jmix-localfs has a Path Traversal in Local File Storage > Attackers can manipulate file references to read arbitrary files on the server via the REST API or database in Jmix applications. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Apr 2025 - **Updated:** 27 May 2025 - **Also known as:** GHSA-jx4g-3xqm-62vh ## What is CVE-2025-32950? CVE-2025-32950 is a medium-severity path traversal vulnerability in jmix-framework jmix, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Jmix is a set of libraries and tools to speed up Spring Boot data-centric application development. In versions 1.0.0 to 1.6.1 and 2.0.0 to 2.3.4, 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. This issue has been patched in versions 1.6.2 and 2.4.0. A workaround is provided on the Jmix documentation website. Weakness: CWE-35 (Path Traversal: '.../...//'), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-32950? 4 open source packages ship an affected version, including io.jmix.localfs:jmix-localfs. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.jmix.localfs:jmix-localfs` | Maven | From 1.0.0 | 1.6.2 | | `io.jmix.localfs:jmix-localfs` | Maven | From 1.0.0 | 1.6.2 | | `io.jmix.localfs:jmix-localfs` | Maven | From 2.0.0 | 2.4.0 | | `io.jmix.localfs:jmix-localfs` | Maven | From 2.0.0 | 2.4.0 | Products: Haulmont Jmix Framework. ## How do I fix CVE-2025-32950? Upgrade io.jmix.localfs:jmix-localfs to a fixed version for your release line: 1.6.2 or 2.4.0. ## Is CVE-2025-32950 being exploited? There is no known exploitation of CVE-2025-32950 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-32950 and fix it if it is affected. What it is: CVE-2025-32950 is a medium-severity path traversal vulnerability in jmix-framework jmix, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-32950 in the wild and no public exploit code. Affected packages and fixed versions: - io.jmix.localfs:jmix-localfs (Maven): affected from 1.0.0; fixed in 1.6.2 - io.jmix.localfs:jmix-localfs (Maven): affected from 1.0.0; fixed in 1.6.2 - io.jmix.localfs:jmix-localfs (Maven): affected from 2.0.0; fixed in 2.4.0 - io.jmix.localfs:jmix-localfs (Maven): affected from 2.0.0; fixed in 2.4.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-32950/ (Markdown: https://insights.sbomify.com/CVE-2025-32950/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32950 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32950 - OSV: https://osv.dev/vulnerability/CVE-2025-32950 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-32950/ Summaries are generated and may contain mistakes; the official description above is the record.