CVE-2026-118504
Deferred Deferred - Pending Action

Improper API Access in Gitea Allows Issue Modifications on Archived Repositories

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: Gitea Limited

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-01
Last Modified
2026-11-01
Generated
2026-11-01
AI Q&A
2026-11-01
EPSS Evaluated
N/A
NVD
CVE-2026-118504

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Gitea Gitea 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an API issue in Gitea where users with write access can bypass repository archive restrictions. The web interface blocks changes to issues in archived repositories, but the API does not consistently enforce this rule. This allows attackers to edit, delete, or alter issues on archived repositories, compromising data integrity.

Detection Guidance

To detect this vulnerability, check if your Gitea instance is running a version <= 28.2.0. Use commands like 'gitea --version' or check the version in the web interface under Site Administration. Verify if API requests to issue-related endpoints (e.g., /api/v1/repos/{owner}/{repo}/issues/{index}) allow modifications on archived repositories.

Impact Analysis

If you use Gitea and have repositories with archived issues, an attacker with write access could modify or delete those issues, labels, or deadlines. This could lead to data loss, unauthorized changes, or disruption of project history, even on archived repositories.

Compliance Impact

This vulnerability could impact compliance by allowing unauthorized modifications to archived data, which may violate integrity requirements in GDPR or HIPAA. Archiving is meant to preserve data integrity, so bypassing these restrictions could lead to non-compliance with data protection regulations.

Mitigation Strategies

Upgrade Gitea to version 28.3.0 or later immediately. This version applies the archive restriction guard to all modifying API requests. If upgrading is not possible, restrict write access to repositories until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-118504. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...