dbcve.org
GokapiApplication · Forceu

CVE-2026-29060

MEDIUM · 5.0 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 2.2.3 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to version 2.2.3, a registered user without privileges to create or modify file requests is able to create a short-lived API key that has the permission to do so. The user must be registered with Gokapi. If there are no users with access to the admin/upload menu, there is no impact. 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 confidence

A broken access control vulnerability in Gokapi allows unprivileged registered users to create short-lived API keys with elevated permissions (to create/modify file requests) that they should not have. This is a privilege escalation issue via API key generation.

MitigationUpgrade to Gokapi version 2.2.3. As a workaround, ensure only trusted users are registered and no unprivileged users exist in the system.

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
GokapiApplication
Affected:< 2.2.3

CVSS 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
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Gokapi installation and version
    Check the web interface footer or query the API endpoint (usually /api/version or /health) to retrieve the running version number
    Affected if The installed version is below 2.2.3
  2. Verify if user registration is enabled
    Inspect the Gokapi configuration file (typically config.json or via the admin web UI) to determine if new user registration is permitted
    Affected if User registration is open and untrusted users can self-register
  3. List existing user accounts and roles
    Access the admin panel (usually at /admin) or query the user API to view all registered users and their permission levels
    Affected if There are registered users with non-admin or limited permissions in the system
  4. Test API key creation as a non-admin user
    Log in with a standard (non-admin) user account and attempt to access the API key generation endpoint (typically under user settings or /api/keys)
    Affected if A non-admin user can successfully generate an API key with elevated or admin-level permissions
  5. Review API key permissions
    After generating an API key as a non-admin user, inspect the key's assigned permissions or test its capabilities against file request creation/modification endpoints
    Affected if The generated API key has permissions beyond what the user account normally possesses

You are affected if running any Gokapi version below 2.2.3 and your system has unprivileged registered users who can access API key generation functionality with elevated permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.2.3 or later
Fixed in 2.2.3
Interim mitigation

Upgrade to Gokapi version 2.2.3. As a workaround, ensure only trusted users are registered and no unprivileged users exist in the system.

Recommended fix High confidence

2.2.3

  1. 1. Check current Gokapi version by accessing the admin interface or checking the running container/process
  2. 2. Back up Gokapi configuration, database, and stored files before upgrading
  3. 3. Upgrade Gokapi to version 2.2.3 or later
  4. 4. Verify the upgrade was successful by checking the version in the admin interface
  5. 5. Ensure no unauthorized API keys exist by reviewing API keys in the admin panel

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gokapi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29060 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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