{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104109 exists.","fix":"No fix has been published for CVE-2026-104109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104109 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-104109 and fix it if it is affected.\n\nWhat it is: CVE-2026-104109 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104109 exists.\n\nAffected product: error311 FileRise. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-104109/ (Markdown: https://insights.sbomify.com/CVE-2026-104109/index.md)","id":"CVE-2026-104109","markdown":"https://insights.sbomify.com/CVE-2026-104109/index.md","name":"CVE-2026-104109","record":{"aliases":["GHSA-jp22-hh6w-mpwp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FileRise file manager","requires_auth":"low_privilege","summary":"Authenticated users can overwrite or delete files outside the storage root via symlink exploitation during ZIP extraction in FileRise.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise validates archive entry names but extracts them directly into the authorized live destination before validating resolved paths. If that destination already contains a symlink to a directory outside the storage root, an authenticated non-administrator with extract permission who can upload or otherwise place an attacker-controlled ZIP in that folder can place an ordinary archive entry beneath the link. ZipArchive::extractTo() can then overwrite an external file, and post-extraction cleanup can delete that target through the same linked parent, only where the FileRise process has the required filesystem write or removal permission. The advisory does not establish that the attacker can create the prerequisite symlink through FileRise. This issue is fixed in version 3.23.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FileRise: Authenticated ZIP extraction follows a pre-existing symlink and deletes files outside the storage root","id":"CVE-2026-104109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in FileRise","id":"CVE-2026-104110"},"packages":[],"prev":{"headline":"FileRise OIDC login can bind an attacker identity to an existing local account","id":"CVE-2026-104108"},"products":["FileRise"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["error311"]},"summary":"Authenticated users can overwrite or delete files outside the storage root via symlink exploitation during ZIP extraction in FileRise.","url":"https://insights.sbomify.com/CVE-2026-104109/"}