CVE-2026-70396

Gitea organization repository creation token scope bypass

Published Oct 14, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions.
Title Gitea organization repository creation token scope bypass
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 18, 2026, 1:31 PM
Reserved
Aug 13, 2026, 4:50 PM
Status
Deferred
Published
Oct 14, 2026, 3:17 PM
Modified
Oct 18, 2026, 2:16 PM