Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2026-30961: 0.26% estimated exploitation activity in the next 30 days; percentile 18.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact Any guest with access to a shared file request link can upload files far larger than the administrator-configured size limit, up to the server's global MaxFileSizeMB. This allows unauthorized storage consumption, circumvention of administrative resource policies, and potential service disruption through storage exhaustion. No data exposure or privilege escalation occurs.

Published by the source

13 Mar 2026, 18:56 UTC

Last modified by the source

24 Mar 2026, 21:02 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-45vh-rpc8-hxpp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30961

Advisory: Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload
IDs: CVE-2026-30961, GHSA-45vh-rpc8-hxpp
Record: https://patchnext.com/advisories/cve-2026-30961 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/forceu/gokapi 2.2.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/forceu/gokapi: affected <= 2.2.3; fixed in 2.2.4

## Suggested inspection (read-only)
- Go github.com/forceu/gokapi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/forceu/gokapi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-45vh-rpc8-hxpp (GitHub-reviewed advisory GHSA-45vh-rpc8-hxpp lists affected ranges: Go github.com/forceu/gokapi >=0 <=2.2.3)

Commands are suggestions: review each one before running it.