# CVE-2026-119625: Gitea token scope bypass in web routes

Source: https://junglewise.ai/threats/cve-2026-119625-the-username-web-route-accepted-personal-access-tokens-over-http  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-01. Updated: 2026-11-01  
License: CC BY 4.0 with a link back

CVE-2026-119625 · Severity: info · Published 2026-11-01

Gitea is a self-hosted Git service that manages code repositories and user accounts. The `/{username}` web route accepted authentication tokens without enforcing scope restrictions, allowing a token with limited permissions to read a user's private activity (RSS/Atom feeds, activity tabs) or view their private repositories and organizations. An attacker with a restricted or public-only token could enumerate sensitive account information.

Technologies: [Gitea](https://junglewise.ai/threats/technologies/gitea). Vendors: [Gitea](https://junglewise.ai/threats/vendors/gitea).

## Quick answers

**Is CVE-2026-119625 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119625 being exploited in the wild.

**How severe is CVE-2026-119625?** Informational severity, published 1 November 2026.

**Which products and versions are affected?** Gitea prior to 28.3.0.

**Is there a fix for CVE-2026-119625?** Yes: fixed in Gitea 28.3.0. Until then: Upgrade to Gitea 28.3.0 or later. As a workaround, restrict external access to Gitea web routes or disable HTTP Basic authentication if not required for automated integrations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119625 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-119625?** Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Gitea 28.3.0

Upgrade to Gitea 28.3.0 or later. As a workaround, restrict external access to Gitea web routes or disable HTTP Basic authentication if not required for automated integrations.

## Technical details

The vulnerability is a token scope bypass in Gitea's web routes. When HTTP Basic authentication with a personal access token was used on the `/{username}` profile route, the server did not validate the token's scope, allowing tokens restricted to unrelated scopes (e.g., `read:issue`) or public-only tokens to access private activity feeds and profile data. The fix restricts token authentication on this route to only feed endpoints and requires `read:user` or `read:organization` scope for feed access.

## Affected products

- Gitea Gitea prior to 28.3.0

## Timeline

- 2026-11-01: disclosed

## References

- [https://blog.gitea.com/release-of-28.3.0/](https://blog.gitea.com/release-of-28.3.0/)
- [https://github.com/go-gitea/gitea/pull/39945](https://github.com/go-gitea/gitea/pull/39945)

## Related threats

- [Gitea account takeover via OAuth2 auto-linking](https://junglewise.ai/threats/cve-2026-120263-when-oauth2-client-account-linking-is-set-to-auto-not-the)
- [Gitea limited-visibility profile disclosure via public-only token](https://junglewise.ai/threats/cve-2026-119627-the-web-profile-and-rss-atom-feed-routes-of-users-and)
- [Gitea project boards information disclosure of private pull requests](https://junglewise.ai/threats/cve-2026-119533-repository-and-organization-project-boards-listed-the-pull)
- [Gitea API token scope bypass in repository deletion](https://junglewise.ai/threats/cve-2026-119441-delete-api-v1-orgs-org-repos-deletes-all-repositories-of-an)
- [Gitea REST API archived repository modification bypass](https://junglewise.ai/threats/cve-2026-118504-the-web-interface-blocks-issue-and-pull-request-changes-on)