{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24897 exists.","fix":"No fix has been published for CVE-2026-24897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24897 is a critical vulnerability in ErugoOSS Erugo, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24897 and fix it if it is affected.\n\nWhat it is: CVE-2026-24897 is a critical vulnerability in ErugoOSS Erugo, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24897 exists.\n\nAffected product: ErugoOSS Erugo. 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-24897/ (Markdown: https://insights.sbomify.com/CVE-2026-24897/index.md)","id":"CVE-2026-24897","markdown":"https://insights.sbomify.com/CVE-2026-24897/index.md","name":"CVE-2026-24897","record":{"aliases":["GHSA-336w-hgpq-6369"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Erugo file sharing","requires_auth":"none","summary":"Authenticated low-privileged users can upload arbitrary files to the web root, leading to remote code execution and full server compromise.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"erugo","vendor":"erugo"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"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":"Erugo is a self-hosted file-sharing platform. In versions up to and including 0.2.14, an authenticated low-privileged user can upload arbitrary files to any specified location due to insufficient validation of user‑supplied paths when creating shares.\nBy specifying a writable path within the public web root, an attacker can upload and execute arbitrary code on the server, resulting in remote code execution (RCE). This vulnerability allows a low-privileged user to fully compromise the affected Erugo instance. Version 0.2.15 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-04-30","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-30","kind":"exploitdb","ref":"52529","stars":null,"title":"Erugo  0.2.14 - Remote Code Execution (RCE)"}],"tier":"weaponised"},"has_fix":false,"headline":"Authenticated Remote Code Execution via Arbitrary File Upload","id":"CVE-2026-24897","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":"OpenEMR has an Unauthenticated MedEx Token Disclosure","id":"CVE-2026-24898"},"packages":[],"prev":{"headline":"OpenEMR has Broken Access Control that allows unauthorized access to EDI Logs","id":"CVE-2026-24896"},"products":["Erugo"],"published":"2026-01-28","related":[],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["ErugoOSS"]},"summary":"Authenticated low-privileged users can upload arbitrary files to the web root, leading to remote code execution and full server compromise.","url":"https://insights.sbomify.com/CVE-2026-24897/"}