# CVE-2026-105174: Gerapy Project Management views.py project_create path traversal

> Attackers can exploit a path traversal vulnerability in Gerapy's project creation feature to read or modify arbitrary files on the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-5chj-52p4-fv78

## What is CVE-2026-105174?

CVE-2026-105174 is a medium-severity path traversal vulnerability in Gerapy, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in Gerapy up to 0.9.13. This vulnerability affects the function project_create of the file gerapy/server/core/views.py of the component Project Management. The manipulation of the argument project_name leads to path traversal. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The identifier of the patch is 6e481078cfba6388a67ca2d9792288405019ba3e. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-105174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105174 is a medium-severity path traversal vulnerability in Gerapy, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105174 exists.

Affected product: Gerapy. 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-105174/ (Markdown: https://insights.sbomify.com/CVE-2026-105174/index.md)
```

## Sources

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

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