Skip to content

← Public intelligence

Maven package

io.jmix.localfs:jmix-localfs

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenPublished

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

    CVE-2025-32952 · GHSA-f3gv-cwwh-758m

    Affected
    • Maven io.jmix.localfs:jmix-localfs >= 1.0.0, < 1.6.2; >= 2.0.0, < 2.4.0
    Fixed in
    2.4.01.6.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.4.0 or 1.6.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.5MavenPublished

    io.jmix.localfs:jmix-localfs has a Path Traversal in Local File Storage

    CVE-2025-32950 · GHSA-jx4g-3xqm-62vh

    Affected
    • Maven io.jmix.localfs:jmix-localfs >= 1.0.0, < 1.6.2; >= 2.0.0, < 2.4.0
    Fixed in
    2.4.01.6.2· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 2.4.0 or 1.6.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →