CVE-2026-116296
Deferred Deferred - Pending Action

GitHub API Write Access Flaw in Archived Repositories

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: Gitea Limited

Description
The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while keeping their download URLs, delete releases and tags, and create, edit or delete milestones and labels of a repository that is meant to be read-only. Changing requests on these routes now return 423 Locked for archived repositories.

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-116296

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-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-116296 is a vulnerability in Gitea where API routes for releases, assets, milestones, and labels do not enforce write-protection for archived repositories. This allows users with write access to modify or delete these elements even when the repository is archived, bypassing intended restrictions.

Detection Guidance

Check Gitea version with 'gitea --version' or via the web UI under Site Administration. If running version 28.2.0 or earlier, the system is vulnerable. Review API logs for unauthorized modifications to archived repositories, such as changes to releases, milestones, or labels.

Impact Analysis

An attacker with write access could replace release binaries, delete releases and their assets, or edit/delete milestones and labels in an archived repository. This could lead to supply chain attacks, data loss, or tampered metadata without detection.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by allowing unauthorized modifications to archived repositories, potentially leading to data integrity issues. For GDPR, unauthorized changes to release assets or metadata may violate integrity requirements for personal data processing. For HIPAA, tampering with archived repositories could compromise the integrity of protected health information stored in releases or associated metadata.

Mitigation Strategies

Upgrade Gitea to version 28.3.0 or later immediately. Revoke write access tokens for users who no longer need it. Monitor API activity for suspicious changes to archived repositories until the upgrade is complete.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116296. 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...