Gitea · Gitea · published 2026-10-06
CVE-2026-89182Gitea push-to-create bypass of FORCE_PRIVATE policy
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-89182 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This Gitea vulnerability: CVSS 5.4 (v3.1). Fixed upstream in Gitea 28.1.0, 28.0.0. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.1.0, 28.0.0.
Patch events
DevOpsGitea
Gitea security releases: 28.1.0, 28.0.0
Upgrade to
28.1.028.0.0Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (10th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.4 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
1.27.0through28.0.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.