CVE-2026-30955
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 2.2.4, An API endpoint accepts unbounded request bodies without any size limit. An authenticated user can cause an OOM kill and complete service disruption for all users. This vulnerability is fixed in 2.2.4.
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 before 2.2.4 have an API endpoint that accepts unbounded request bodies without any size limit. An authenticated user can send excessively large requests to trigger an out-of-memory condition, causing the service to crash and denying service to all users.
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.4CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Determine installed Gokapi versionRun 'gokapi --version' or check the binary/version file typically found in the Gokapi installation directoryAffected if The version number is less than 2.2.4
-
Verify API endpoint is accessibleCheck network configuration or firewall rules to confirm the API port (commonly 53842) is exposed to network usersAffected if The API is reachable from untrusted networks or the endpoint responds to requests
-
Confirm authentication is enabledReview Gokapi configuration file (usually config.json) for 'RequireAuthentication' or similar settingsAffected if Authentication is disabled or set to allow anonymous API access
-
Check for request body size limitsInspect the configuration file for any 'MaxBodySize', 'RequestLimit', or similar settings that limit incoming request sizesAffected if No body size limit is configured or the limit is set to an extremely high value/unlimited
You are affected if Gokapi version is below 2.2.4 AND the API endpoint is accessible with authenticated users able to send large requests without enforced size limits.
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.4
Upgrade to Gokapi version 2.2.4 or later which implements proper request body size limits to prevent OOM-based DoS attacks.
2.2.4
- Backup your existing Gokapi data and configuration files
- Stop the current Gokapi service
- Download Gokapi version 2.2.4 from the official GitHub releases repository
- Replace the existing Gokapi binary with the new version 2.2.4
- Restart the Gokapi service
- Verify the service is running correctly and the API endpoint now enforces request body size limits
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30955 — 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-30955 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