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

Published Oct 18, 2026
·
Updated

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.

Affected Software

1 affected component
Gitea Gitea

Event History

Oct 18, 2026
CVE Published
via MITRE·06:56 PM
Data Sourced
via MITRE·06:56 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionWeakness

Frequently Asked Questions

1

Who can trigger the failure?

Any unauthenticated remote requester can trigger it by requesting the repositories route for an individual user. No special configuration is required.

2

What is the impact of a successful request?

Each request causes the server to return HTTP 500 and log a panic. The corrected behavior is HTTP 404 when the route is used for an individual user.

3

How can I identify attempted exploitation or exposure in logs?

Look for HTTP 500 responses and corresponding panic logs associated with requests matching /{username}/-/repositories where the username belongs to an individual user.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203