# CVE-2026-109844: Gitea watched repositories API disclosure after access revocation

> Attackers can view metadata of private repositories they no longer have access to via the subscriptions API, exposing sensitive project details.

- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-96gv-2xc4-4hxj

## What is CVE-2026-109844?

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

### Official description

`GET /api/v1/user/subscriptions` returned the metadata of every repository a user was watching without checking that the user still had access to it. A user who watched a private repository while having access, and later lost it, for example through a team permission downgrade, could still read its name, description, clone URLs, owner and counters. The issue was fixed in 1.27.0 and 28.0.0 and disclosed with 28.2.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109844 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109844 is a medium-severity vulnerability in Gitea, published on 18 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-109844 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-109844/ (Markdown: https://insights.sbomify.com/CVE-2026-109844/index.md)
```

## Sources

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

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