Gitea push-to-create bypass of FORCE_PRIVATE policy
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-89182US | —OT elevated | — | ||
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 reposi… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-28.1.0/ARTICLE
- https://github.com/go-gitea/gitea/pull/39501FIX
- https://github.com/go-gitea/gitea/pull/39507FIX
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0ARTICLE
- https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgcADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2026-89182WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan