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' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39945 patch
- https://github.com/go-gitea/gitea/pull/40115 patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenunscored · giteaNVD modified 2026-11-01 09:48
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/go-gitea/gitea/security/advisories/GHSA-3fv3-hhmm-4x2q vendor-advisory
- https://github.com/go-gitea/gitea/pull/39945 patch
- https://github.com/go-gitea/gitea/pull/40115 patch
- https://blog.gitea.com/release-of-28.3.0/ release-notes
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0 release-notes