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

> Repository administrators can bypass team access restrictions to grant organization teams unauthorized repository access, requiring a patch.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-g5jj-gp8w-73h7

## What is CVE-2026-60010?

CVE-2026-60010 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

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

Weakness: CWE-863 (Incorrect Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-60010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60010 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60010 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-60010/ (Markdown: https://insights.sbomify.com/CVE-2026-60010/index.md)
```

## Sources

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

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