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.
28.4.0Exploitability
AV:NAC:LPR:LUI:NScope
S:UImpact
C:LI:HA:H8.3/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:HOther