CVE-2026-123638 (GCVE-0-2026-123638)
Vulnerability from cvelistv5 – Published: 2026-11-15 21:14 – Updated: 2026-11-15 21:14
VLAI
EPSS
VEX
Title
Gitea protected file pattern bypass with quoted file names
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.
Severity
No CVSS data available.
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/go-gitea/gitea/security/adviso… | vendor-advisory |
| https://github.com/go-gitea/gitea/pull/40362 | patch |
| https://blog.gitea.com/release-of-28.4.0/ | release-notes |
| https://github.com/go-gitea/gitea/releases/tag/v28.4.0 | release-notes |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageName": "gitea.dev",
"product": "Gitea",
"vendor": "Gitea",
"versions": [
{
"lessThan": "28.4.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "https://github.com/Bryan-Project"
},
{
"lang": "en",
"type": "reporter",
"value": "https://github.com/yagcioglutoprak"
},
{
"lang": "en",
"type": "remediation developer",
"value": "https://github.com/lunny"
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository\u0027s runners. Changed files are now listed unquoted, and a rename reports both the old and the new path."
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-15T21:14:03.522Z",
"orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"shortName": "Gitea"
},
"references": [
{
"name": "GitHub Security Advisory GHSA-w87g-xmrp-86v2",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-w87g-xmrp-86v2"
},
{
"name": "Fix on release/v28: go-gitea/gitea pull request #40362",
"tags": [
"patch"
],
"url": "https://github.com/go-gitea/gitea/pull/40362"
},
{
"name": "Gitea 28.4.0 release announcement",
"tags": [
"release-notes"
],
"url": "https://blog.gitea.com/release-of-28.4.0/"
},
{
"name": "go-gitea/gitea v28.4.0 release",
"tags": [
"release-notes"
],
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.4.0"
}
],
"title": "Gitea protected file pattern bypass with quoted file names"
}
},
"cveMetadata": {
"assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"assignerShortName": "Gitea",
"cveId": "CVE-2026-123638",
"datePublished": "2026-11-15T21:14:03.522Z",
"dateReserved": "2026-11-15T20:29:37.618Z",
"dateUpdated": "2026-11-15T21:14:03.522Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-123638",
"date": "2026-11-16",
"epss": "0.00244",
"percentile": "0.15758"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"packageName": "gitea.dev",
"product": "Gitea",
"vendor": "Gitea",
"versions": [
{
"lessThan": "28.4.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository\u0027s runners. Changed files are now listed unquoted, and a rename reports both the old and the new path."
}
],
"id": "CVE-2026-123638",
"lastModified": "2026-11-15T22:17:18.553",
"metrics": {},
"published": "2026-11-15T22:17:18.453",
"references": [
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://blog.gitea.com/release-of-28.4.0/"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/pull/40362"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.4.0"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-w87g-xmrp-86v2"
}
],
"sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-693"
}
],
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"type": "Secondary"
}
]
}
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…