Skip to main content
Report · Reddit NetSecAbout CVE-2026-117635Published

CVE-2026-117635: Gitea scope bypass found · a "public-only" token can reach the whole admin API, including creating a new site admin

Source Reddit NetSec

0
Compare
Authoritative record:CVE-2026-117635· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 28.3.0 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.16.5
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 28.3.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade Gitea and github.com/go-gitea/gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • <28.3.0
Fixed in
  • 28.3.0
Gogithub.com/go-gitea/giteapkg:golang/github.com/go-gitea/giteaOther threatsAffected
  • <28.3.0
Fixed in
  • 28.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Gitea to version 28.3.0 or later, where the vulnerability is fixed. After upgrading, review the list of site administrators and remove any unrecognized accounts. Also audit Actions runners and runner registration tokens for unauthorized entries. Note that revoking leaked tokens does not remove accounts created by the exploit, so manual cleanup is required.

Discussion

A scope bypass vulnerability (CVE-2026-117635) in Gitea allowed a "public-only" access token to access the entire admin API. This flaw enabled such tokens, which should be limited to public resources, to list private organizations and user emails, create new users, promote them to site administrators, and mint Actions runner registration tokens. The issue was due to missing scope checks on the admin API routes. It is fixed in Gitea version 28.3.0. Users are advised to upgrade and audit their admin accounts and Actions runners for unauthorized changes.

r/netsec (opens in a new tab)u/PriorPuzzleheaded8800 points0 comments

We found a scope bypass where a Gitea access token restricted to public resources could do everything the admin API allows.

Gitea enforces “public only” on the normal API routes. So if you ask for a private org with that token and you get token scope is limited to public orgs.

But then if you ask /api/v1/admin/orgs for the same org with the same token, it returns it.

The restriction is enforced one route group at a time, and essentially the admin group never got a check. Because the admin API has no public subset to narrow to, the narrowing middleware wouldn't have helped either. What was missing was the check for an outright reject.

A public-only token with write:admin, issued from a site-admin account, could:

  • list every private org and every user’s email
  • create a user and promote it to site admin
  • mint Actions runner registration tokens

If you self-host Gitea, upgrade to v28.3.0. Then check your site-admin list and your Actions runners for anything you don’t recognize.

Takeaway for any API with scoped tokens: when the scope is checked per route group, look for the groups that never call the check. Also look for groups that call a check with nothing to restrict.

(Gitea’s fix attaches the scope to the authenticated user instead, so no route group has to remember it.)

If you're interested the full write-up is here: https://escape.tech/blog/escape-research-found-a-scope-bypass-that-made-gitea-s-restricted-tokens-full-admins-it-s-now-cve-2026-117635/

Full disclosure: I work at Escape, the team that did the research.

References

Community reviews

Loading reviews…