Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 07 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 07 Oct 2026 04:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Tue, 06 Oct 2026 21:45:00 +0000
| 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 |
|
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-10-07T11:34:42.708Z
Reserved: 2026-10-04T22:02:04.881Z
Link: CVE-2026-89182
Updated: 2026-10-07T11:33:37.603Z
Status : Awaiting Analysis
Published: 2026-10-06T22:17:07.690
Modified: 2026-10-07T13:45:36.947
Link: CVE-2026-89182
No data.
OpenCVE Enrichment
Updated: 2026-10-07T13:45:06Z
-
CWE-863
Incorrect Authorization