Skip to main content
Menu
CVEs

CVE

Gitea protected file pattern bypass via quoted names

Affects Gitea versions before 28.4.0 where a branch protection rule uses Protected file patterns. The fix is in Gitea 28.4.0.

CVE-2026-123638EUVD-2026-126124

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

8.3HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 28.4.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. A branch protection rule uses Protected file patterns

Published
Last modified
Reference
Last checked
0.24% · 15th percentile
16/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Gitea's branch protection feature, which uses "Protected file patterns" to guard certain files, can be bypassed when file names contain double quotes, backslashes, or control characters. A user with write access could then add or change protected files, including workflow files that run on the repository's runners, or rename a protected file to move it out of the pattern.

Original description

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.

Who should check

Teams running Gitea 28.3.0 or earlier with branch protection Protected file patterns, including those protecting .gitea/** workflow paths.

“branch-protection Protected file patterns feature”

github.com

cve.now Index

16Pcve.now Index 16 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.3/10CVSS 8.3
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    A branch protection rule uses Protected file patterns
  • Upgrade to a fixed version: 28.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123638 (Gitea protected file pattern bypass with quoted file names), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123638 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: fixed in 28.4.0
Fixed versions: 28.4.0.
Conditions (all must be true for the bug to be hit):
- A branch protection rule uses Protected file patterns (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-w87g-xmrp-86v2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-123638 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123638 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-w87g-xmrp-86v2
- https://github.com/go-gitea/gitea/pull/40362
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123638
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123638"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • gitea.dev

    fixed in 28.4.0

Evidence 6

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Patch
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123638

Is CVE-2026-123638 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A user with write access can create or change files under protected patterns by naming them with quoted file names. This includes adding workflow files that run on self-hosted runners.Source: github.com

Which versions are affected by CVE-2026-123638?

gitea.dev: before 28.4.0.Source: cve.now feed data

Am I affected, and how do I check?

Gitea versions before 28.4.0 are affected when a branch protection rule uses the Protected file patterns feature. To check a setup, look at the installed Gitea version and at whether any branch protection rule has Protected file patterns set.Source: github.com

How do I fix CVE-2026-123638?

Upgrade Gitea to 28.4.0 or later. The facts do not name a separate patch or workaround.Source: github.com