Bug 2574055 (CVE-2026-123638) - CVE-2026-123638 gitea: gitea: Protected file pattern bypass via quoted file names
Summary: CVE-2026-123638 gitea: gitea: Protected file pattern bypass via quoted file n...
Keywords:
Status: NEW
Alias: CVE-2026-123638
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-16 21:58 UTC by OSIDB Bzimport
Modified: 2026-11-17 01:14 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-16 21:58:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.