Gitea · Gitea · published 2026-11-15
CVE-2026-129337Gitea push without write access to repositories still being created
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-129337 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 11% of all CVEs. This Gitea vulnerability: CVSS 5.3 (v3.1). Fixed upstream in Gitea 28.4.0, 28.3.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.4.0, 28.3.0.
Patch events
DevOpsGitea
Gitea security releases: 28.4.0, 28.3.0
Upgrade to
28.4.028.3.0Why: Vendor security release for server software (most severe: CVE-2026-118389).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (11th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
1.16.0to before28.4.0(affected)
Description (from the CVE record)#
Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.
Quoted from the CVE Program record.