CVE-2026-56654
CRITICAL
CVSS 9.8
code.gitea.io/gitea
Verified Advisory
Privilege escalation via Personal Access Token scope bypass in Gitea (CVE-2026-56654)
Gitea's API endpoint for creating Personal Access Tokens (`POST /users/{username}/tokens`) can be accessed using an existing token formatted as `Authorization: Basic <token>:x-oauth-basic`. The Basic auth handler sets `AuthedMethod="basic"`, causing `IsBasicAuth=true` and bypassing the `reqBasicOrRevProxyAuth` middleware that is intended to require password-based authentication. Because the token creation handler enforces no scope ceiling, an attacker with any restricted token can create a new fully-privileged `all`-scoped token without knowing the account password.
Affected versions:
- <= 1.26.4
We recommend updating to: 1.27.0.
CVSS ? · our assessment: this_week
Reference: https://github.com/go-gitea/gitea/security/advisories/GHSA-683j-3ff6-hh2x
Details: https://vuln.today/cve/CVE-2026-56654
Verified by vuln.today against published advisories.
Affected versions
- – <= 1.26.4
Fixed in: 1.27.0
More advisories for code.gitea.io/gitea
- CVE-2026-55982 – OIDC userinfo scope bypass in Gitea (CVE-2026-55982)
- CVE-2026-20706 – Token scope bypass on archive download endpoint in Gitea (CVE-2026-20706)
- CVE-2026-58314 – Server-side request forgery in Gitea hostmatcher and OpenID sign-in (CVE-2026-58314)
- CVE-2026-58436 – Quadratic-time denial of service in Gitea Locale middleware (CVE-2026-58436)
- CVE-2026-58437 – Repository visibility manipulation via undocumented git push options in Gitea (CVE-2026-58437)
- CVE-2026-55987 – Account deactivation bypass via OAuth2 sign-in in Gitea (CVE-2026-55987)
- CVE-2026-54481 – Improper certificate validation in Gitea internal API HTTP client (CVE-2026-54481)
- CVE-2026-58443 – Authorization bypass in Gitea pull request update API endpoint (CVE-2026-58443)