Technical impact
The vulnerability allows a user with write access to a Gitea repository to add or modify files that match protected patterns defined in a branch protection rule. Git prints file names with quoting when they contain a double quote, backslash, or control character; the protected file match test incorrectly used unquoted names, so quoted names never matched a pattern. An attacker can therefore push or merge a file that would normally be blocked, or rename a protected file to remove it from the pattern. When the protected pattern covers workflow files, this permits insertion of a workflow that runs on repository runners, leading to remote code execution. The issue is classified as CWE-693.
Affected Systems
All Gitea instances running a version earlier than 28.4.0 are vulnerable. The official fix was introduced in release 28.4.0 and applies to all later versions. No other vendors or product lines are affected.
Risk and Exploitability
Exploitation requires only that the attacker have normal write privileges to the target repository, a condition common in many projects. Based on the description, it is inferred that an attacker can push a malicious workflow or rename a protected file through a direct push or a pull‑request merge. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Nonetheless, because the vulnerability enables arbitrary code execution on the repository’s runners, the risk is high for affected installations.