Gitea issue attachment API allows changing comment attachments
The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.
- Products
- gitea
- Affected versions
- Not specified
- Fixed versions
- 28.1.0
- CVEs
- CVE-2026-105268
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 12:11 UTC · Revision 1
Source evidence
Gitea issue attachment API allows changing comment attachments
core-osv · Original sourcePublished 14 Oct 2026, 08:42 UTC
The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.
osv:BIT-gitea-2026-105268
gitea
Fixed versions: 28.1.0
Complete source record
{
"id": "2ebae03274dba5daca35b390ee0af607d3735011a44395769fe9df92206294aa",
"url": "https://osv.dev/vulnerability/BIT-gitea-2026-105268",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Gitea issue attachment API allows changing comment attachments",
"summary": "The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.",
"evidence": "osv:BIT-gitea-2026-105268",
"products": [
{
"name": {
"value": "gitea",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "28.1.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "BIT-gitea-2026-105268",
"aliases": [
"BIT-gitea-2026-105268",
"CVE-2026-105268",
"GHSA-96qg-qxxj-r8xq"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "28.1.0"
}
]
}
],
"package": {
"name": "gitea",
"purl": "pkg:bitnami/gitea",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/gitea/BIT-gitea-2026-105268.json"
}
}
],
"modified": "2026-10-14T11:11:13.285102006Z",
"provider": "osv",
"references": [
"https://blog.gitea.com/release-of-28.1.0/",
"https://github.com/go-gitea/gitea/pull/39501",
"https://github.com/go-gitea/gitea/pull/39507",
"https://github.com/go-gitea/gitea/releases/tag/v28.1.0",
"https://github.com/go-gitea/gitea/security/advisories/GHSA-96qg-qxxj-r8xq",
"https://nvd.nist.gov/vuln/detail/CVE-2026-105268"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
],
"severity": "Medium"
}
},
"related_cves": [
{
"value": "CVE-2026-105268",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 316259,
"published_at": "2026-10-14T08:42:44.006+00:00"
}