CVE-2026-73804

Gitea is vulnerable to API token scope escalation via HTTP signatures due to a flaw in how request scopes are validated. An attacker with a token possessing only the write:user scope can use that token to register an attacker-controlled SSH public key on the token owner's account via the POST /ap...

CVE-2026-73804

Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing route-level token scop...

CVE-2026-73126

Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A token lacking read:repository, or restricted to public repositories, can retrieve the latest workflow status of a private repository...

CVE-2026-73126

Gitea versions

CVE-2026-70407 Gitea organization listing token scope bypass

Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...

CVE-2026-70407

The Gitea organization-list API (endpoint GET /api/v1/orgs) fails to enforce the read:organization token scope. Consequently, a token with a different category, such as read:misc , can retrieve organization metadata visible to its owner. If the token belongs to a site administrator , the response...

CVE-2026-70407 Gitea organization listing token scope bypass

Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...

CVE-2026-70407

Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...

CVE-2026-70406 Gitea private comparison disclosure with public-only tokens

Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit history and diffs from a private head...

CVE-2026-70406

Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit history and diffs from a private head...

CVE-2026-70400 Gitea private migration creation with public-only tokens

Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing account or an organization where that...

CVE-2026-70396

The Gitea organization repository-creation API (specifically POST /api/v1/orgs/{org}/repos) is vulnerable to a token scope bypass due to incorrect authorization. While the API correctly requires the write:organization scope, it fails to enforce the write:repository scope required by other reposit...

CVE-2026-70396 Gitea organization repository creation token scope bypass

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

CVE-2026-70396 Gitea organization repository creation token scope bypass

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

CVE-2026-70396

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

CVE-2026-20896

Proof of Concept Code CVE-2026-20896 This script automates the exploitation of the logic flaw in Gitea's API route validation, allowing to force the server to grant a valid administrative token through a Directory Traversal attack in the authorization header. !/usr/bin/env python3 PoC: Gitea...

EUVD-2026-100982

When base64 data is split up in pieces, of 3 character or less, tokens were incorrectly calculated to produce 0 bytes. This enables attackers to overwrite the stack with up to 64K of attacker controlled data. Zone files which are written out by NSD itself, such as for zones for which the NSD...

CVE-2018-15133-laravel-framework

CVE-2018-15133 - Laravel Framework 5.6.x Vulnerable Lab This repo provides a reproducible Docker lab for CVE-2018-15133 Laravel Framework token unserialize RCE when APPKEY is known. The app is pinned to a vulnerable Laravel 5.6.x version and exposes a simple /poc POST route under the web middlewa...

CVE-2026-109971 Clevis: clevis: pkcs#11 token pin exposed on command line via pkcs11-tool

A flaw was found in the clevis PKCS11 pin. The clevis-decrypt-pkcs11 script passes the PKCS11 token PIN as a command-line argument to pkcs11-tool, making it visible to any local user through process listing or the /proc filesystem...

CVE-2026-109971

A flaw exists in the clevis PKCS#11 pin where the clevis-decrypt-pkcs11 script passes the PKCS#11 token PIN as a command-line argument to pkcs11-tool . This exposure allows any local user to view the sensitive PIN via process listing or the /proc filesystem. No specific remediation or exploit inf...