# CVE-2026-66853: Gitea restricted-user organization metadata disclosure

> Restricted users can view limited-visibility organization metadata via the list API, exposing hidden names and descriptions.

- **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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-w4wc-g858-3672

## What is CVE-2026-66853?

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

### Official description

Gitea's user organization-list API includes Limited-visibility organizations for authenticated restricted accounts without applying the visibility restriction enforced by the single-organization endpoint. A restricted user can list a known user's public organization memberships and retrieve limited organizations' names, descriptions, and avatars. This exposes organization metadata that should be hidden from the requesting account.

Weakness: CWE-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-66853 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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