Is github.com/forceu/gokapi 1.2 vulnerable?
Go · 1 release from 1.2.0 to 1.2.0 · latest github.com/forceu/gokapi is 1.9.6 · checked 18 Nov 2026
Yes: 20 known advisories
Yes. github.com/forceu/gokapi 1.2.0, the last 1.2 release, is affected by 20 known security advisories (1 high, 9 medium, 10 low), including CVE-2026-28683, CVE-2026-30961, CVE-2026-30955. At least one has no fixed release yet.
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
Advisories affecting github.com/forceu/gokapi 1.2.0
Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi vulnerable to Privilege Escalation in File Replace in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi vulnerable to DoS in E2E Metadata Parser in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Gokapi vulnerable to DoS in E2E Metadata Parser
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Gokapi vulnerable to Privilege Escalation in File Replace
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Gokapi has Stored XSS in SVG Hotlinks in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi has Data Leak in Upload Status Stream in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi has privilege escalation with auth token in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi has CSRF in Login Endpoint in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi has privilege escalation via incomplete API-key permission revocation on user rank demotion in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi has CSRF in Login Endpoint
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Gokapi has privilege escalation via incomplete API-key permission revocation on user rank demotion
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Gokapi has privilege escalation with auth token
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Gokapi has Stored XSS in SVG Hotlinks
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Gokapi has Data Leak in Upload Status Stream
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Gokapi has stored XSS vulnerability in friendly name for API keys in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi vulnerable to stored XSS via uploading file with malicious file name in github.com/forceu/gokapi
- Affected
- All versions
- Fixed in
- No fix released
Gokapi vulnerable to stored XSS via uploading file with malicious file name
- Affected
- >=1.0.1 <=1.9.6 · <0.0.0-20250530191232-343cc566cfd7
- Fixed in
- 0.0.0-20250530191232-343cc566cfd7
Gokapi has stored XSS vulnerability in friendly name for API keys
- Affected
- >=1.0.1 <=1.9.6 · <0.0.0-20250530185940-65ddbc68fbfd
- Fixed in
- 0.0.0-20250530185940-65ddbc68fbfd
Which of your client projects are still on github.com/forceu/gokapi 1.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/forceu/gokapi version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/forceu/gokapi versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.