CVE-2026-123638
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…
Impact
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.
An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: low risk of data being read, high risk of data or systems being changed, high risk of outages.
Affected products · Gitea
| Product | Affected versions |
|---|---|
| Gitea | before 28.4.0 |