CVE-2026-25575
Path Traversal in NavigaTUM propose_edits Allows File Overwrite
Publication date: 2026-02-04
Last updated on: 2026-02-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tum | navigatum | to 2026-02-03 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-26 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory. |
| CWE-23 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability is a path traversal issue in the propose_edits endpoint of the NavigaTUM website and API. It allows unauthenticated users to overwrite files in directories writable by the application user by supplying unsanitized file keys containing traversal sequences like "../../" in the JSON payload. This enables attackers to escape the intended temporary directory and replace public-facing images or fill the server's storage.
How can this vulnerability impact me? :
This vulnerability can allow attackers to overwrite important files in writable directories, potentially replacing public-facing images or filling the server's storage. This can lead to defacement of the website, denial of service due to storage exhaustion, or other malicious impacts on the availability and integrity of the application.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched via commit 86f34c7. Immediate steps to mitigate this vulnerability include updating the NavigaTUM application to include this patch.
Additionally, restricting write permissions on directories writable by the application user (such as /cdn) can help reduce the risk of exploitation.