# CVE-2026-25575: NavigaTUM has a Path Traversal Vulnerability in the propose_edits functionality

> Unauthenticated attackers can overwrite files or fill storage via path traversal in the propose_edits endpoint of NavigaTUM.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-59hj-f48w-hjfm

## What is CVE-2026-25575?

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.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-26 (Path Traversal: '/dir/../filename'), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-25575?

It affects 1 product.


Products: Tum Navigatum.

## How do I fix CVE-2026-25575?

No fix has been published for CVE-2026-25575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25575 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25575 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25575 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25575 exists.

Affected product: TUM-Dev NavigaTUM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25575/ (Markdown: https://insights.sbomify.com/CVE-2026-25575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25575
- OSV: https://osv.dev/vulnerability/CVE-2026-25575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25575/
Summaries are generated and may contain mistakes; the official description above is the record.