{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26984 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26984 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26984 is a high-severity vulnerability in aces Loris, published on 25 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26984 and fix it if it is affected.\n\nWhat it is: CVE-2026-26984 is a high-severity vulnerability in aces Loris, published on 25 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26984 in the wild and no public exploit code.\n\nAffected product: aces Loris. 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-26984/ (Markdown: https://insights.sbomify.com/CVE-2026-26984/index.md)","id":"CVE-2026-26984","markdown":"https://insights.sbomify.com/CVE-2026-26984/index.md","name":"CVE-2026-26984","record":{"aliases":["GHSA-mpgc-c48m-6v2h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Neuroimaging research platform","requires_auth":"high_privilege","summary":"Authenticated users can exploit path traversal to upload malicious files, leading to remote code execution on the LORIS server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"loris","vendor":"mcgill"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. Prior to versions 26.0.5, 27.0.2, and 28.0.0, an authenticated user with sufficient privileges can exploit a path traversal vulnerability to upload a malicious file to an arbitrary location on the server. Once uploaded, the file can be used to achieve remote code execution (RCE). An attacker must be authenticated and have the appropriate permissions to exploit this issue. If the server is configured as read-only, remote code execution (RCE) is not possible; however, the malicious file upload may still be achievable. This problem is fixed in LORIS v26.0.5 and above, v27.0.2 and above, and v28.0.0 and above. As a workaround, LORIS administrators can disable the media module if it is not being used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"LORIS media module vulnerable to remote code execution","id":"CVE-2026-26984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"LORIS vulnerable to path traversal in electrophysiology_browser","id":"CVE-2026-26985"},"packages":[],"prev":{"headline":"ImageMagick: Invalid MSL \u003cmap\u003e can result in a use after free","id":"CVE-2026-26983"},"products":["Loris"],"published":"2026-02-25","related":[{"cvss_score":8.7,"headline":"LORIS has potential cross-site scripting in help_editor module","id":"CVE-2026-35169","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":8.1,"headline":"LORIS vulnerable to path traversal in electrophysiology_browser","id":"CVE-2026-26985","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":7.7,"headline":"LORIS has a path traversal in FilesDownloadHandler","id":"CVE-2026-35446","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"LORIS has a SQL injection in MRI feedback popup","id":"CVE-2026-33350","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"LORIS has a path traversal in static router","id":"CVE-2026-34392","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":6.5,"headline":"LORIS has potential cross-site scripting in survey_accounts module","id":"CVE-2026-35403","kev_date_added":null,"published":"2026-04-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["aces"]},"summary":"Authenticated users can exploit path traversal to upload malicious files, leading to remote code execution on the LORIS server.","url":"https://insights.sbomify.com/CVE-2026-26984/"}