Gitea: Incomplete CVE-2025-68941 fix: /user/orgs missing checkTokenPublicOnly + switch-case logic flaw

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:L/I:N/A:N

EPSS

• CVE-2026-25714: 0.39% estimated exploitation activity in the next 30 days; percentile 33.47 (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 Two related issues in the token public-only scope enforcement introduced by PR #32204 (CVE-2025-68941 fix). A public-only scoped API token can access private organization data. Issue 1: /user/orgs missing checkTokenPublicOnly() routers/api/v1/api.go line 1599: Adjacent route at line 1603 has it: Issue 2: checkTokenPublicOnly switch-case evaluates only first matching category routers/api/v1/api.go lines 253-295. Go switch executes only the first matching case. For routes with categories [User, Organization]: 1. Organization case matches first (line 263) 2. ctx.Org.Organization is nil on user routes, passes 3. ctx.ContextUser.IsOrganization() is false, passes 4. User case (line 273) is never reached 5. User visibility check skipped entirely Steps to Reproduce 1. Create a token with public-only scope (Settings Applications check "public only") 2. Call: curl -H "Authorization: token <PUBLICONLYTOKEN" https://gitea.example.com/api/v1/user/orgs 3. Response includes private and…

Published by the source

16 Jun 2026, 23:41 UTC

Last modified by the source

16 Jun 2026, 23:41 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8629-vc8r-5p58

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

# Patch Next advisory brief: CVE-2026-25714

Advisory: Gitea: Incomplete CVE-2025-68941 fix: /user/orgs missing checkTokenPublicOnly + switch-case logic flaw
IDs: CVE-2026-25714, GHSA-8629-vc8r-5p58
Record: https://patchnext.com/advisories/cve-2026-25714 (revision 1, source checked 26 Oct 2026, 15:24 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: code.gitea.io/gitea 1.26.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.gitea.io/gitea: affected <= 1.26.1; fixed in 1.26.2

## Suggested inspection (read-only)
- Go code.gitea.io/gitea: 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 code.gitea.io/gitea.
- 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-8629-vc8r-5p58 (GitHub-reviewed advisory GHSA-8629-vc8r-5p58 lists affected ranges: Go code.gitea.io/gitea >=0 <=1.26.1)

Commands are suggestions: review each one before running it.