Gokapi has CSRF in Login Endpoint

Exploitation

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

CVSS

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

EPSS

• CVE-2026-29084: 0.08% estimated exploitation activity in the next 30 days; percentile 0.26 (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 login flow accepts credential-bearing requests without CSRF protection mechanisms tied to the browser session context. The handler parses form values directly and creates a session on successful credential validation. Issue found by aisafe.io Impact An attacker can force a victim browser into a session associated with an existing user account where the attacker knows the credentials, causing user confusion, activity misattribution, and potential misuse of trusted user actions.

Published by the source

5 Mar 2026, 20:43 UTC

Last modified by the source

8 Mar 2026, 08:37 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hcff-qv74-7hr4

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

# Patch Next advisory brief: CVE-2026-29084

Advisory: Gokapi has CSRF in Login Endpoint
IDs: CVE-2026-29084, GHSA-hcff-qv74-7hr4
Record: https://patchnext.com/advisories/cve-2026-29084 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
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.3. 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.3

## 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-hcff-qv74-7hr4 (GitHub-reviewed advisory GHSA-hcff-qv74-7hr4 lists affected ranges: Go github.com/forceu/gokapi >=0 <2.2.3)

Commands are suggestions: review each one before running it.