# CVE-2026-27761: Gitea repository feeds bypass API token scope enforcement

> Attackers can use API tokens lacking repository scope to access private commit data via RSS and Atom feed endpoints 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:** Yes
- **Published:** 3 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-3pww-vcvm-3gmj, GO-2026-6031

## What is CVE-2026-27761?

CVE-2026-27761 is a medium-severity missing authorization vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.

Weakness: CWE-863 (Incorrect Authorization)

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

3 open source packages ship an affected version, including code.gitea.io/gitea.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |

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

Upgrade code.gitea.io/gitea to 1.26.3 or later.

## Is CVE-2026-27761 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27761 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27761 is a medium-severity missing authorization vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27761 exists.

Affected packages and fixed versions:
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3

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-27761/ (Markdown: https://insights.sbomify.com/CVE-2026-27761/index.md)
```

## Sources

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

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