Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private

Exploitation

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

CVSS

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

EPSS

• CVE-2026-24451: 0.45% estimated exploitation activity in the next 30 days; percentile 39.07 (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 POST /api/v1/repos/{owner}/{repo}/merge-upstream endpoint continues to synchronize commits from a parent repository after the parent repository has been changed from public to private. A fork created while the parent repository was public can still receive commits made after the parent repository becomes private. As a result, content added during the private period becomes available through the fork repository after synchronization. Details Gitea provides the merge-upstream API to synchronize a fork with its parent repository. A typical workflow is: 1. A repository is public. 2. Another user creates a fork. 3. The fork owner uses merge-upstream to receive updates from the parent repository. However, if the parent repository is later changed from public to private, the synchronization endpoint continues to import new commits from the parent repository into the fork. In testing on Gitea 1.26.2, a fork owner who can no longer directly access the parent repository is still…

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 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wrf9-r3h7-7x5v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-6081

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

# Patch Next advisory brief: CVE-2026-24451

Advisory: Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private
IDs: CVE-2026-24451, GHSA-wrf9-r3h7-7x5v
Record: https://patchnext.com/advisories/cve-2026-24451 (revision 2, 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: High (CVSS 7.5)
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.3. A vendor fix does not mean a deployment is fixed.

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

## 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-6081 (OSV record GO-2026-6081 lists affected ranges: Go code.gitea.io/gitea >=0 <1.26.3 (fixed))
- Verified: https://github.com/advisories/GHSA-wrf9-r3h7-7x5v (GitHub-reviewed advisory GHSA-wrf9-r3h7-7x5v lists affected ranges: Go code.gitea.io/gitea >=0 <1.26.3)

Commands are suggestions: review each one before running it.