Quick answers
- Is CVE-2026-112887 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112887 being exploited in the wild.
- How severe is CVE-2026-112887?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea prior to 28.3.0.
- Is there a fix for CVE-2026-112887?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112887 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112887?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.3.0
Technical details
Actions task tokens lack API scope restrictions and authenticate as a system user with a negative ID. Repository and organization filters in the REST API treated the negative ID as "no owner filter" rather than a non-existent owner, allowing GET /api/v1/user/repos to list every repository including private ones. The fix ensures system users own nothing by checking != 0 in ownership filters and restricts /api/v1/user routes to individual and bot accounts only.
Affected products
- Gitea Gitea prior to 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched