CVE-2026-89182

Gitea push-to-create bypass of FORCE_PRIVATE policy

Published Oct 6, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.

Remediation

No solution or workaround provided in the CVE record

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': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', '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 With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.
Title Gitea push-to-create bypass of FORCE_PRIVATE policy
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 11:34 AM
Reserved
Oct 4, 2026, 10:02 PM
Status
Analyzed
Published
Oct 6, 2026, 10:17 PM
Modified
Oct 13, 2026, 6:03 PM