Skip to main content
VulnerabilityPublished

CVE-2026-28682: Forceu Gokapi · Improper Access Control

Affects Forceu GokapiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium : upgrade to 2.2.3 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 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.3.

Affected software

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

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

AI-suggested

To mitigate this vulnerability, organizations should upgrade Gokapi to version 2.2.3 or later, where the issue is patched. Until the upgrade is applied, administrators should restrict access to the /uploadStatus SSE endpoint to only trusted users and monitor authentication logs for suspicious activity. Implementing strict user authentication and session management can reduce the risk of unauthorized access. Additionally, consider isolating user sessions or deploying separate instances of Gokapi for different user groups to limit cross-user data exposure. Regularly audit access control configurations and review server logs for anomalous subscription patterns to the SSE endpoint. Employ network segmentation and firewall rules to limit access to the file sharing server from untrusted networks. Finally, educate users about the importance of safeguarding their credentials to prevent unauthorized authenticated access.

Description

Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. Prior to version 2.2.3, the upload status SSE implementation on /uploadStatus publishes global upload state to any authenticated listener and includes file_id values that are not scoped to the requesting user. This issue has been patched in version 2.2.3.

References

Community reviews

Loading reviews…