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.
{
"cna_assigner": "Gitea",
"cwe_ids": [
"CWE-693"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/123xxx/CVE-2026-123638.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "28.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"original_tag": "v28.4.0",
"range": [
{
"fixed": "0b5dfdeeeaadf6350314246c5936b53cce38170c"
}
],
"source": "REFERENCES_TAG"
}
]
}