Quick answers
- Is CVE-2026-119441 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119441 being exploited in the wild.
- How severe is CVE-2026-119441?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-119441?
- Yes: fixed in Gitea 28.3.0. Until then: Restrict the creation and use of public-only API tokens; audit token permissions and immediately revoke any public-only tokens held by organization owners until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119441 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119441?
- 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
Restrict the creation and use of public-only API tokens; audit token permissions and immediately revoke any public-only tokens held by organization owners until upgrading.
Technical details
The DELETE /api/v1/orgs/{org}/repos endpoint failed to enforce the public-only scope restriction, checking only that the organization itself was public rather than validating the token's scope. An organization owner holding a public-only token could thereby delete private repositories, which the token should not be able to access. The fix enforces scope validation on organization-ownership-requiring routes.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched