Gitea · Gitea · published 2026-11-15
CVE-2026-123638Gitea protected file pattern bypass with quoted file names
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-123638 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This Gitea vulnerability: CVSS 8.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.4% (31th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H | 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
0to before28.4.0(affected)
Description (from the CVE record)#
The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.
Quoted from the CVE Program record.