CVE-2026-118504 (GCVE-0-2026-118504)
Vulnerability from cvelistv5
Published
2026-11-01 09:48
Modified
2026-11-01 09:48
Severity ?
VLAI Severity ?
EPSS score ?
Summary
The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and deadlines, add or delete tracked time and stopwatches, add reactions, change issue blocks, and pin issues, altering data that archiving is meant to freeze. Gitea 28.2.0 added the check to the issue edit, delete and label routes; Gitea 28.3.0 applies it to all modifying repository API requests.
References
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageName": "gitea.dev",
"product": "Gitea",
"vendor": "Gitea",
"versions": [
{
"lessThan": "28.3.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "https://github.com/DevNoScope"
},
{
"lang": "en",
"type": "reporter",
"value": "https://github.com/nithissh7"
},
{
"lang": "en",
"type": "remediation developer",
"value": "https://github.com/bircni"
}
],
"descriptions": [
{
"lang": "en",
"value": "The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and deadlines, add or delete tracked time and stopwatches, add reactions, change issue blocks, and pin issues, altering data that archiving is meant to freeze. Gitea 28.2.0 added the check to the issue edit, delete and label routes; Gitea 28.3.0 applies it to all modifying repository API requests."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-01T09:48:52.593Z",
"orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"shortName": "Gitea"
},
"references": [
{
"name": "GitHub Security Advisory GHSA-vmrc-8q2x-573x",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-vmrc-8q2x-573x"
},
{
"name": "Partial fix (issue edit, delete and labels): go-gitea/gitea pull request #39839",
"tags": [
"patch"
],
"url": "https://github.com/go-gitea/gitea/pull/39839"
},
{
"name": "Partial fix backport to release/v28: go-gitea/gitea pull request #39847",
"tags": [
"patch"
],
"url": "https://github.com/go-gitea/gitea/pull/39847"
},
{
"name": "Fix: go-gitea/gitea pull request #39942",
"tags": [
"patch"
],
"url": "https://github.com/go-gitea/gitea/pull/39942"
},
{
"name": "Fix backport to release/v28: go-gitea/gitea pull request #40085",
"tags": [
"patch"
],
"url": "https://github.com/go-gitea/gitea/pull/40085"
},
{
"name": "Gitea 28.3.0 release announcement",
"tags": [
"release-notes"
],
"url": "https://blog.gitea.com/release-of-28.3.0/"
},
{
"name": "go-gitea/gitea v28.3.0 release",
"tags": [
"release-notes"
],
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.3.0"
}
],
"title": "Gitea issue changes on archived repositories through the API"
}
},
"cveMetadata": {
"assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"assignerShortName": "Gitea",
"cveId": "CVE-2026-118504",
"datePublished": "2026-11-01T09:48:52.593Z",
"dateReserved": "2026-11-01T08:50:49.243Z",
"dateUpdated": "2026-11-01T09:48:52.593Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…