CVE-2026-29061
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGokapi 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGokapi versions prior to 2.2.3 contain a privilege escalation vulnerability in the user rank demotion logic. When an administrator demotes a user, the user's existing API keys retain ApiPermManageFileRequests and ApiPermManageLogs permissions, allowing continued unauthorized access to upload-request management and log viewing endpoints after the user has been stripped of all privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Gokapi versionLocate the Gokapi binary or Docker container and run 'gokapi --version' or inspect the container metadata to determine the version numberAffected if The version is below 2.2.3
-
Identify user and API key storageExamine the Gokapi data directory for user configuration files or database (typically a users.json, sqlite database, or similar storage based on Gokapi's architecture)Affected if User data storage exists and contains any user records
-
Find demoted user accountsReview user records to identify any accounts that have been assigned a rank lower than 'admin' or have had their privileges reducedAffected if Any user account has been demoted from a higher rank to a lower one
-
Inspect API key permissions for demoted usersFor each demoted user, examine their associated API keys and check if ApiPermManageFileRequests or ApiPermManageLogs permissions are still granted to those keysAffected if A demoted user's API keys retain ApiPermManageFileRequests or ApiPermManageLogs permissions despite the user having no such privileges in their current rank
-
Verify permission mismatchCompare each demoted user's current rank/privileges against the permissions assigned to their API keys - any API key permission that exceeds the user's current rank indicates the vulnerabilityAffected if Any API key permission exists that allows access beyond what the user's current rank permits
If Gokapi version is below 2.2.3 and any demoted user has API keys that still grant ApiPermManageFileRequests or ApiPermManageLogs permissions, the environment is affected by this privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.3
Upgrade Gokapi to version 2.2.3 or later to patch the improper privilege management vulnerability in the user demotion logic.
2.2.3
- Back up your Gokapi data directory and configuration files before proceeding
- Stop the running Gokapi service
- Download Gokapi version 2.2.3 from the official GitHub releases repository
- Replace the existing Gokapi binary with the new version 2.2.3 binary
- Start the Gokapi service
- Verify the upgrade was successful by checking the version number in the admin interface or via API
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data