Skip to main content
No exploitation reported

CVE-2026-123638

Gitea protected file pattern bypass with quoted file names

No exploitation reported by the sources we read.

  • Published2026-11-15
  • WeaknessCWE-693

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1521:14CVE publishedCNA

Versions per branch

Products declared by the CNA

As Gitea, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • Giteaother versions: not affected

    package gitea.dev

    Affected
    • < 28.4.0fixed in 28.4.0semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-15

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-123638 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-11-16
  • CISA-ADPSSVC decisionnone2026-11-16
  • CISA-ADPCVSS 3.18.32026-11-16
  • CNAweakness (CWE)CWE-6932026-11-15

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Published
2026-11-15
Last Modified
2026-11-16
NVD status
Deferred

Frequently asked questions

What is CVE-2026-123638?

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.

Is CVE-2026-123638 actively exploited?

Active exploitation of CVE-2026-123638 has not been confirmed.

What is the CVSS score for CVE-2026-123638?

CVE-2026-123638 has a CVSS v3 base score of 8.3 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record