Skip to content
Fencer Intel
high 8.3

CVE-2026-123638 json

Gitea protected file pattern bypass with quoted file names

published 2d ago modified yesterday also EUVD-2026-126124 , GHSA-w87g-xmrp-86v2

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • go gitea.dev 28.4.0
  • Gitea Gitea 28.4.0

Is CVE-2026-123638 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-17).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Affected packages

ecosystem package affected fixed in
go gitea.dev
<=28.3.0
28.4.0

Affected products

  • Gitea Gitea

Classification

Weakness
  • CWE-693 Protection Mechanism Failure
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.