# CVE-2026-30961: Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload

> Attackers can bypass file size limits on public file requests by uploading oversized files in multiple chunks, potentially exhausting server storage.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 13 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-45vh-rpc8-hxpp, GO-2026-4695

## What is CVE-2026-30961?

CVE-2026-30961 is a medium-severity vulnerability in Forceu Gokapi, published on 13 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 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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.4 |
| `github.com/forceu/gokapi` | Go | All versions | 2.2.4 |

Products: Forceu Gokapi.

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

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

## Is CVE-2026-30961 being exploited?

There is no known exploitation of CVE-2026-30961 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-28682](https://insights.sbomify.com/CVE-2026-28682/): Gokapi: Data Leak in Upload Status Stream (medium 6.4)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30961 is a medium-severity vulnerability in Forceu Gokapi, published on 13 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-30961 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.4
- github.com/forceu/gokapi (Go): affected all versions; fixed in 2.2.4

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-30961/ (Markdown: https://insights.sbomify.com/CVE-2026-30961/index.md)
```

## Sources

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

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