CVE-2026-97208

Gitea push mirror API bypass of DISABLE_NEW_PUSH policy

Published Oct 6, 2026 CVSS 3.1 · 4.9 Medium EPSS < 1% KEV · Not listed
Description
The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.

Analysis

AI-generated

Technical impact

The Gitea push mirror creation endpoint allows a repository administrator to set up mirrors without the system enforcing the DISABLE_NEW_PUSH policy that is normally applied through the web interface. This enables private repository data to be copied to an attacker‑controlled remote location whenever commits occur or a mirror is scheduled, constituting a breach of confidentiality. The vulnerability stems from insufficient access‑control validation (CWE‑863).

Affected Systems

All installations of the Gitea product that run a version older than the patched 28.1.0 release are potentially vulnerable because the fix that checks the DISABLE_NEW_PUSH setting was introduced in that release. The application is the Gitea web service, and the affected API endpoint is POST /api/v1/repos/{owner}/{repo}/push_mirrors. Inferences about the specific affected versions are based on the release notes cited in the advisory.

Risk and Exploitability

The path to exploitation requires the attacker to be authenticated as a repository administrator and to send a POST request to the push_mirrors endpoint. No publicly released exploit is known, and the EPSS score of less than 1% indicates that exploitation activity is likely very low. The vulnerability is not listed in the CISA KEV catalog. The low CVSS score of 4.9 suggests the overall severity is low to moderate, but the flaw still permits confidential data to be replicated without authorization. The likely attack vector is an authenticated API request from a compromised or privileged account.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.1.0 or newer, which enforces the DISABLE_NEW_PUSH policy when mirrors are created.
  • If an upgrade cannot be performed immediately, disable push mirror creation globally in the system configuration or revoke API access for all repository administrators until the patch is applied.
  • Limit the scope of repository administrator privileges so that only trusted users have access to the push_mirrors API, reducing the risk that a compromised credential can be used to create unauthorized mirrors.

Generated by OpenCVE AI on October 7, 2026 at 23:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.
Title Gitea push mirror API bypass of DISABLE_NEW_PUSH policy
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 8:05 PM
Reserved
Oct 4, 2026, 9:59 PM
Status
Analyzed
Published
Oct 6, 2026, 10:17 PM
Modified
Oct 13, 2026, 5:56 PM