247 matches found
CVE-2026-123272
A flaw was found in mcp-go. A malicious Model Context Protocol MCP server can declare arbitrary protected resources within its metadata due to improper validation in the OAuth metadata handler. This flaw allows an attacker to cause the authorization server to issue tokens scoped for unintended...
CVE-2026-114199
A flaw was found in Gitea. An authenticated user possessing a restricted, public-only access token can trigger an information disclosure vulnerability by querying the user contribution heatmap API endpoint. Due to improper enforcement of token scope restrictions, the endpoint computes activity da...
CVE-2026-119625 Gitea user and organization feed token scope bypass
The /username web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as read:issue, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members'...
redmine -- multiple vulnerabilities
Redmine reports: High: ReDoS in wiki macro argument parsing 44657. Affects 6.0.0 and later; fixed in 7.0.3, 6.1.6 and 6.0.12. High: OAuth token scope is ignored in Project.allowedtocondition 44625. Affects 6.1.0 and later; fixed in 7.0.3 and 6.1.6. High: Private project names and role assignments...
EUVD-2026-110600
Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session...
CVE-2026-12664 Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an authenticated user with a readapi-scoped token to retrieve a project's incoming email address and create...
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 ...
EUVD-2026-101108
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-73804
Gitea is vulnerable to a privilege escalation flaw where an attacker can register an attacker-controlled SSH public key on a token owner's account using a token with write:user scope. Subsequent API requests signed with the corresponding private key authenticate via HTTP Signature without providi...
CVE-2026-73126
Gitea versions
CVE-2026-73126 Gitea private workflow badge token scope bypass
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-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-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...
EUVD-2026-101097
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 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-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 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 ...