CVE-2026-117635: Gitea admin API public-only token scope bypass
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. A public-only token with admin scope issued by a site administrator could therefore list private organizations and the email addresses of all users, create organizations, obtain runner registration tokens and create new site administrator accounts, the last of which persists after the token is revoked. Tokens of users who are not site administrators cannot reach these routes; public-only tokens are now rejected on the admin API.
Description quoted from the CVE record (assigned by Gitea, published 2026-11-01).
Weakness: CWE-284: Improper Access Control; CWE-1259: Improper Restriction of Security Token Assignment
How it can be exploited
Exploitable over the network with low attack complexity needing high privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 2 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 3 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.049
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Gitea (gitea.dev) | before 28.3.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 28.3.0.
Vendor guidance:
- GitHub Security Advisory GHSA-37xv-m4w7-j2fh (vendor-advisory)
- Fix: go-gitea/gitea pull request #39690 (patch)
- Fix backport to release/v28: go-gitea/gitea pull request #39853 (patch)
- Gitea 28.3.0 release announcement (release-notes)
- go-gitea/gitea v28.3.0 release (release-notes)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Vendor advisories and patches
- GitHub Security Advisory GHSA-37xv-m4w7-j2fh (vendor-advisory)
- Fix: go-gitea/gitea pull request #39690 (patch)
- Fix backport to release/v28: go-gitea/gitea pull request #39853 (patch)
- Gitea 28.3.0 release announcement (release-notes)
- go-gitea/gitea v28.3.0 release (release-notes)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners