Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions

Exploitation

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

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The API endpoint used to fork repositories into organizations performs a weaker authorization check than the corresponding web UI and other repository creation endpoints. When a repository is forked into an organization through the API, the endpoint only verifies that the user is an organization member (IsOrgMember()), but does not verify whether the user is allowed to create repositories in that organization (CanCreateOrgRepo()). As a result, organization members belonging to teams with cancreateorgrepo=false can still create repositories inside the organization by using the fork API. Details Affected endpoint: In routers/api/v1/repo/fork.go, the endpoint performs the following authorization check: The equivalent web UI implementation uses the stronger permission check: The same CanCreateOrgRepo() authorization check is also used by: CreateOrgRepo API endpoint GenerateRepository API endpoint The fork endpoint appears to be the only repository creation path that relies solely…

Published by the source

27 Jul 2026, 15:32 UTC

Last modified by the source

27 Jul 2026, 17:00 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rjvx-x5h2-6px5

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-6074

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

# Patch Next advisory brief: GHSA-rjvx-x5h2-6px5

Advisory: Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions
IDs: GHSA-rjvx-x5h2-6px5
Record: https://patchnext.com/advisories/go-2026-6074 (revision 3, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.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.0. A vendor fix does not mean a deployment is fixed.

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

## 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://osv.dev/vulnerability/GO-2026-6074 (OSV record GO-2026-6074 lists affected ranges: Go code.gitea.io/gitea >=0 <1.26.0 (fixed))
- Verified: https://github.com/advisories/GHSA-rjvx-x5h2-6px5 (GitHub-reviewed advisory GHSA-rjvx-x5h2-6px5 lists affected ranges: Go code.gitea.io/gitea >=0 <1.26.0)

Commands are suggestions: review each one before running it.