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

> Attackers with limited-scope tokens can bypass authorization checks to read private organization metadata in Gitea.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-ww9q-7j5q-hrv5

## What is CVE-2026-70407?

CVE-2026-70407 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-70407?


## How do I fix CVE-2026-70407?

No fix has been published for CVE-2026-70407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70407 being exploited?

There is no known exploitation of CVE-2026-70407 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70407 and fix it if it is affected.

What it is: CVE-2026-70407 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70407 in the wild and no public exploit code.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70407/ (Markdown: https://insights.sbomify.com/CVE-2026-70407/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70407
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70407
- OSV: https://osv.dev/vulnerability/CVE-2026-70407

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70407/
Summaries are generated and may contain mistakes; the official description above is the record.