Gerapy CVE-2026-105174

Exploitation requires an authenticated session on the Gerapy server (CVSS PR:L), since the fix also re-adds @permission_classes([IsAuthenticated]) to the affected project-management endpoint. The attacker must reach the Project Management feature and either supply a crafted project_name or upload a project ZIP archive containing entries with ../ traversal sequences that are expanded relative to PROJECTS_FOLDER during extraction. Limiting factors: valid credentials are needed, impact is confined to file write/integrity and limited availability (no confidentiality per VC:N), and only Gerapy versions up to 0.9.13 are affected. No special non-default configuration is indicated beyond having the project upload/create functionality in use.

This is a moderate, not top-priority, issue. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L) scores 5.3 (Medium): network-reachable and low-complexity, but requiring low-level privileges (PR:L = authenticated) and yielding only limited integrity and availability impact with no confidentiality loss. The E:P sub-metric and the 'POC publicly available' signal indicate publicly available exploit code exists, but there is NO CISA KEV listing and no EPSS score provided, so there is no evidence of active or widespread exploitation - exploit availability is a distinct, lower-urgency signal than confirmed in-the-wild use. A notable data conflict exists: the CVE description attributes path traversal to the function project_create via the project_name argument, but the actual patch diff (PR #319) fixes a Zip Slip in project_upload's zipfile.extractall and separately re-enables @permission_classes([IsAuthenticated]) on project_create - verify the exact vulnerable sink with the vendor, as the described function and the patched code do not cleanly align. The requirement for authentication (PR:L) and the fact that Gerapy is a niche self-hosted tool substantially limit real-world risk despite network reachability.

An authenticated low-privileged Gerapy user submits a crafted project name or uploads a malicious project archive whose entries contain path-traversal sequences (../), causing files to be written outside the intended PROJECTS_FOLDER when the server extracts or creates the project. Public exploit code referenced in the Gerapy GitHub issue (#317) exists, and because the vector is network-based with low complexity (AV:N/AC:L), a logged-in attacker can trigger it with a single crafted request.