Gitea · Gitea · published 2026-11-15
CVE-2026-125423Gitea command execution through repository auto-initialization
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-125423 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 22% of all CVEs. This Gitea vulnerability: CVSS 8.8 (v3.1), a successful attack gives total control of the component. 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.3% (23th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0to before28.4.0(affected)
Description (from the CVE record)#
A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.
Quoted from the CVE Program record.