# CVE-2026-28682: Gokapi: Data Leak in Upload Status Stream

> An authenticated attacker can view file IDs of other users via the upload status stream, leaking sensitive metadata.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-c36c-7pc2-f2ph, GO-2026-4613

## What is CVE-2026-28682?

CVE-2026-28682 is a medium-severity vulnerability in Forceu Gokapi, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-28682?

3 open source packages ship an affected version, including github.com/forceu/gokapi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/forceu/gokapi` | Go | All versions | None |
| `github.com/forceu/gokapi` | Go | All versions | 2.2.3 |
| `github.com/forceu/gokapi` | Go | All versions | 2.2.3 |

Products: Forceu Gokapi.

## How do I fix CVE-2026-28682?

Upgrade github.com/forceu/gokapi to 2.2.3 or later.

## Is CVE-2026-28682 being exploited?

There is no known exploitation of CVE-2026-28682 in the wild and no public exploit code.

## Other vulnerabilities in Forceu Gokapi

- [CVE-2026-28683](https://insights.sbomify.com/CVE-2026-28683/): Gokapi: Stored XSS in SVG Hotlinks (high 8.7)
- [CVE-2026-30955](https://insights.sbomify.com/CVE-2026-30955/): Gokapi vulnerable to DoS in E2E Metadata Parser (medium 6.5)
- [CVE-2026-29061](https://insights.sbomify.com/CVE-2026-29061/): Gokapi: Privilege escalation via incomplete API-key permission revocation on user rank demotion (medium 5.4)
- [CVE-2026-29060](https://insights.sbomify.com/CVE-2026-29060/): Gokapi: Privilege escalation with auth token (medium 5.0)
- [CVE-2025-48494](https://insights.sbomify.com/CVE-2025-48494/): Gokapi vulnerable to stored XSS via uploading file with malicious file name (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28682 and fix it if it is affected.

What it is: CVE-2026-28682 is a medium-severity vulnerability in Forceu Gokapi, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28682 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/forceu/gokapi (Go): affected all versions; no fix listed
- github.com/forceu/gokapi (Go): affected all versions; fixed in 2.2.3
- github.com/forceu/gokapi (Go): affected all versions; fixed in 2.2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-28682/ (Markdown: https://insights.sbomify.com/CVE-2026-28682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28682
- OSV: https://osv.dev/vulnerability/CVE-2026-28682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-28682/
Summaries are generated and may contain mistakes; the official description above is the record.