CVEsGiteaCVE-2026-119625Published Nov 1, 09:48 · Updated Nov 1, 09:48 UTC
–
Not scored
CVE-2026-119625

Gitea user and organization feed token scope bypass

gitea.dev · Incorrect authorization · CWE-863
Affectedgitea.dev
FixUpdate to 28.3.0 or newer
PublishedNov 1, 09:48 · Gitea
ScoredNot yet
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:08 UTC

What we know

No known exploitation. CISA KEV, checked 22:08 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
No severity score yet.

Description

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

From Gitea

Affected and fixed versions

ProductAffectedFixed ingitea.devbefore 28.3.028.3.0

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

GitHub Security Advisory GHSA-3fv3-hhmm-4x2q · github.comvendor advisoryFix: go-gitea/gitea pull request #39945 · github.compatchFix backport to release/v28: go-gitea/gitea pull request #40115 · github.compatchGitea 28.3.0 release announcement · blog.gitea.comrelease notesgo-gitea/gitea v28.3.0 release · github.comrelease notes

Other CVEs in gitea.dev

All 70 →
–Gitea limited-visibility profile disclosure with public-only tokens · CVE-2026-119627Nov 1–Gitea private pull request disclosure on project boards · CVE-2026-119533Nov 1–Gitea public-only token bypass on bulk organization repository deletion · CVE-2026-119441Nov 1