Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-30961: CWE-770: Allocation of Resources Without Limits or Throttling in Forceu Gokapi

0
Medium
VulnerabilityCVE-2026-30961cvecve-2026-30961cwe-770
Published: Fri Mar 13 2026 (03/13/2026, 19:09:38 UTC)
Source: CVE Database V5
Vendor/Project: Forceu
Product: Gokapi

Description

Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to 2.2.4, the chunked upload completion path for file requests does not validate the total file size against the per-request MaxSize limit. An attacker with a public file request link can split an oversized file into chunks each under MaxSize and upload them sequentially, bypassing the size restriction entirely. Files up to the server's global MaxFileSizeMB are accepted regardless of the file request's configured limit. This vulnerability is fixed in 2.2.4.

AI-Powered Analysis

AILast updated: 03/13/2026, 19:44:17 UTC

Technical Analysis

The vulnerability identified as CVE-2026-30961 affects Forceu's Gokapi, a self-hosted file sharing server that supports automatic expiration and encryption. Prior to version 2.2.4, the chunked upload completion mechanism fails to validate the total file size against the configured per-request MaxSize limit. Specifically, an attacker possessing a public file request link can circumvent the intended size restriction by splitting a large file into multiple smaller chunks, each individually under the MaxSize threshold. These chunks are uploaded sequentially, and the server erroneously accepts the entire file as valid, up to the global MaxFileSizeMB limit configured on the server. This flaw stems from an allocation of resources without proper limits or throttling, classified under CWE-770. The vulnerability does not require user interaction and can be exploited remotely with low privileges. While the confidentiality and integrity of data are not directly compromised, the unchecked acceptance of oversized files can lead to resource exhaustion, impacting server availability and performance. The issue was publicly disclosed on March 13, 2026, and has a CVSS v3.1 base score of 4.3 (medium severity). The fix was implemented in Gokapi version 2.2.4, which properly enforces the per-request MaxSize limit during chunked uploads.

Potential Impact

The primary impact of this vulnerability is on the availability of the Gokapi server. By bypassing the per-request file size limit, an attacker can upload very large files in chunks, consuming excessive disk space, memory, and processing resources. This can degrade server performance, cause denial of service conditions, or disrupt legitimate file sharing operations. Organizations relying on Gokapi for secure and efficient file sharing may experience service interruptions or increased operational costs due to resource exhaustion. Although the vulnerability does not expose sensitive data or allow unauthorized data modification, the denial of service potential can affect business continuity, especially in environments with high file sharing demands or limited server capacity. Additionally, the vulnerability could be leveraged as part of a larger attack chain to distract or overwhelm defenders. Since exploitation requires only a public file request link, any exposed or shared links are potential attack vectors, increasing the risk in publicly accessible deployments.

Mitigation Recommendations

The primary mitigation is to upgrade Gokapi to version 2.2.4 or later, where the vulnerability is fixed by enforcing the per-request MaxSize limit during chunked uploads. Until upgrading is possible, administrators should implement strict monitoring of upload sizes and rates, setting alerts for unusual or excessive chunked upload activity. Configuring global MaxFileSizeMB to a conservative value can reduce potential resource exhaustion. Network-level controls such as rate limiting and IP reputation filtering can help limit abusive upload attempts. Additionally, restricting public file request link distribution and implementing authentication or access controls on file requests can reduce exposure. Regularly auditing server resource usage and logs for anomalies related to chunked uploads is recommended. Finally, consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious chunked upload patterns.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-07T17:34:39.981Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b465b22f860ef9438da289

Added to database: 3/13/2026, 7:29:54 PM

Last enriched: 3/13/2026, 7:44:17 PM

Last updated: 3/13/2026, 8:36:30 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses