Protected file pattern bypass in Gitea with quoted file names
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-693.
Summary
Gitea versions from 0 before 28.4.0 check the Protected file patterns setting of branch protection rules against file names as git prints them, and git quotes names containing a double quote, a backslash or a control character. Such names never match a pattern, so a user with write access can add or change files under a protected pattern by direct push or pull request merge. Where the patterns protect workflow files, a user can add a workflow that then runs on the repository's runners.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Gitea to version 28.4.0 or later, which lists changed files unquoted and reports both the old and new path on a rename.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA Gitea (Gitea) Fixed in 28.4.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Gitea 28.4.0
19 records Highest priority Priority LOW 19 LOW
Other records, highest priority first
- TI-2026-91976 Command execution in Gitea through repository auto-initializationPriority LOW 39
- TI-2026-91982 Gitea missing attempt limit for TOTP passcodesPriority LOW 34
- TI-2026-91989 Gitea exposes pending pull request reviews created through the APIPriority LOW 29
Timeline
- 2026-11-15 Threatist record created from CVE-2026-123638
- 2026-11-16 CVSS score added · CISA ADP
- 2026-11-16 CISA SSVC decision points changed
References
More Gitea vulnerabilities
- TI-2026-42785 Remote code execution in Gitea diffpatch API through Git hooks KEVCVSS 3.1CRITICAL 9.8
- TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
- TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
- TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
- TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
- TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences