Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-q658-hfpg-35qc | Gokapi has privilege escalation via incomplete API-key permission revocation on user rank demotion |
Mon, 09 Mar 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:forceu:gokapi:*:*:*:*:*:*:*:* |
Fri, 06 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 06 Mar 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Forceu
Forceu gokapi |
|
| Vendors & Products |
Forceu
Forceu gokapi |
Fri, 06 Mar 2026 05:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to version 2.2.3, a privilege escalation vulnerability in the user rank demotion logic allows a demoted user's existing API keys to retain ApiPermManageFileRequests and ApiPermManageLogs permissions, enabling continued access to upload-request management and log viewing endpoints after the user has been stripped of all privileges. This issue has been patched in version 2.2.3. | |
| Title | Gokapi: Privilege escalation via incomplete API-key permission revocation on user rank demotion | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-06T16:06:23.367Z
Reserved: 2026-03-03T17:50:11.245Z
Link: CVE-2026-29061
Updated: 2026-03-06T15:50:32.424Z
Status : Analyzed
Published: 2026-03-06T05:16:40.903
Modified: 2026-03-09T18:50:07.253
Link: CVE-2026-29061
No data.
OpenCVE Enrichment
Updated: 2026-04-16T11:45:26Z
Github GHSA