Gokapi has Data Leak in Upload Status Stream
Published 5 Mar 2026 · Updated 23 Mar 2026
Is your project on an affected github.com/forceu/gokapi?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <2.2.3
- Fixed in
- 2.2.3
go get github.com/forceu/gokapi@v2.2.3Details
Description
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.
Impact
Any authenticated user can observe other users' file identifiers and retrieve unauthorized content, causing cross-tenant data exposure and loss of confidentiality for uploaded documents.
*Issue found by aisafe.io*
Is GHSA-c36c-7pc2-f2ph in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/forceu/gokapi, and gives you the command that fixes it.
More advisories for github.com/forceu/gokapi
- LowCVE-2026-30961Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload in github.com/forceu/gokapi · 16 Mar 2026
- LowCVE-2026-30943Gokapi vulnerable to Privilege Escalation in File Replace in github.com/forceu/gokapi · 16 Mar 2026
- LowCVE-2026-30955Gokapi vulnerable to DoS in E2E Metadata Parser in github.com/forceu/gokapi · 16 Mar 2026
- MediumCVE-2026-30961Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload · 13 Mar 2026
- MediumCVE-2026-30955Gokapi vulnerable to DoS in E2E Metadata Parser · 13 Mar 2026
- MediumCVE-2026-30943Gokapi vulnerable to Privilege Escalation in File Replace · 13 Mar 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.