All vulnerabilities

Servers and applications

CVE-2026-123638

Gitea protected file pattern bypass with quoted file names

Severity
High 8.3
Published
15 Nov 2026
Last changed
16 Nov 2026
Added to UpHeron
15 Nov 2026
Fixed in
28.4.0
Exploit chance
0.4% in the next 30 daysHigher than 30% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Protection mechanism failure (CWE-693)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read some data · Change data · Take it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Sources
CVE Program

Description

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.

From the CVE Program.

Affected software

SoftwareAffected versions
GiteaServers and applications · cna:gitea|gitea
  • Every version before 28.4.0

About Gitea

free forge based on git written in Go

From Wikidata, CC0 1.0.
Docker Hub pulls
395,154,663Docker Hub, 15 Nov 2026
GitHub stars
59,090GitHub, 15 Nov 2026
Forks
7,394GitHub, 15 Nov 2026
Latest release
v28.3.0GitHub, 15 Nov 2026
Released
1 Nov 2026GitHub
Developer
Jiahua ChenWikidata
License
MIT LicenseWikidata
Written in
Go, JavaScriptWikidata
First released
17 Oct 2016Wikidata
First published on GitHub
1 Nov 2016GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-123638