CVE-2025-32950 is a medium-severity (CVSS 6.5) Path Traversal 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 has a Path Traversal in Local File Storage
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-32950.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-32950 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.jmix.localfs:jmix-localfs☕io.jmix.localfs:jmix-localfsReal-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
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jmix.localfs:jmix-localfs | ≥ 1.0.0&&< 1.6.2 | 1.6.2io.jmix.localfs:jmix-localfs:1.6.2 |
| ☕Maven | io.jmix.localfs:jmix-localfs | ≥ 2.0.0&&< 2.4.0 | 2.4.0io.jmix.localfs:jmix-localfs:2.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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-32950 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-32950 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-32950. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-32950 in your dependencies?
O3 Security finds CVE-2025-32950 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.