Skip to main content
VulnerabilityPublished

CVE-2026-30955: Forceu Gokapi · Uncontrolled Resource Consumption

Affects Forceu GokapiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.4 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Gokapi and forceu/Gokapi to 2.2.4.

Affected software

ProductAffectedFixed in
ForceuGokapiAffected
  • <2.2.4
Fixed in
  • 2.2.4
GitHubforceu/Gokapipkg:github/forceu/GokapiOther threatsAffected
  • <2.2.4
Fixed in
  • 2.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade Gokapi to version 2.2.4 or later, where the vulnerability is fixed. If immediate upgrade is not feasible, administrators should implement strict API gateway or web application firewall (WAF) rules to limit request body sizes on the vulnerable endpoint. Monitoring and alerting on abnormal request sizes and resource usage can help detect exploitation attempts early. Enforcing strong authentication and access controls reduces the risk of malicious authenticated users. Additionally, isolating the Gokapi service in resource-limited containers or virtual machines can prevent system-wide OOM kills. Regularly auditing user accounts and session activity helps identify potential insider threats. Finally, maintaining updated backups and incident response plans ensures rapid recovery from potential service disruptions.

Description

Gokapi 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.

References

Community reviews

Loading reviews…