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.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://github.com/go-gitea/gitea/pull/39501 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39507 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc Mitigation, Vendor Advisory
- https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.4 · giteaNVD modified 2026-10-13 18:03
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 6
- https://blog.gitea.com/release-of-28.1.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39501 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39507 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc Mitigation, Vendor Advisory
- https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc Mitigation, Vendor Advisory