{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25575 exists.","fix":"No fix has been published for CVE-2026-25575 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25575 is a high-severity path traversal vulnerability in TUM-Dev NavigaTUM, published on 4 Feb 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-25575 and fix it if it is affected.\n\nWhat it is: CVE-2026-25575 is a high-severity path traversal vulnerability in TUM-Dev NavigaTUM, published on 4 Feb 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-25575 exists.\n\nAffected product: TUM-Dev NavigaTUM. 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-25575/ (Markdown: https://insights.sbomify.com/CVE-2026-25575/index.md)","id":"CVE-2026-25575","markdown":"https://insights.sbomify.com/CVE-2026-25575/index.md","name":"CVE-2026-25575","record":{"aliases":["GHSA-59hj-f48w-hjfm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NavigaTUM web application","requires_auth":"none","summary":"Unauthenticated attackers can overwrite files or fill storage via path traversal in the propose_edits endpoint of NavigaTUM.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"navigatum","vendor":"tum"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-26","name":"Path Traversal: '/dir/../filename'"},{"id":"CWE-23","name":"Relative Path Traversal"}],"description":"NavigaTUM is a website and API to search for rooms, buildings and other places. Prior to commit 86f34c7, there is a path traversal vulnerability in the propose_edits endpoint allows unauthenticated users to overwrite files in directories writable by the application user (e.g., /cdn). By supplying unsanitized file keys containing traversal sequences (e.g., ../../) in the JSON payload, an attacker can escape the intended temporary directory and replace public facing images or fill the server's storage. This issue has been patched via commit 86f34c7.","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":"NavigaTUM has a Path Traversal Vulnerability in the propose_edits functionality","id":"CVE-2026-25575","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":"ImageMagick: Out of bounds read in multiple coders read raw pixel data","id":"CVE-2026-25576"},"packages":[],"prev":{"headline":"Payload Affected by Cross-Collection IDOR in payload-preferences Access Control (Multi-Auth Environments)","id":"CVE-2026-25574"},"products":["NavigaTUM"],"published":"2026-02-04","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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-05","vendors":["TUM-Dev"]},"summary":"Unauthenticated attackers can overwrite files or fill storage via path traversal in the propose_edits endpoint of NavigaTUM.","url":"https://insights.sbomify.com/CVE-2026-25575/"}