Quick answers
- Is CVE-2026-119627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119627 being exploited in the wild.
- How severe is CVE-2026-119627?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-119627?
- Yes: fixed in Gitea 28.3.0. Until then: Upgrade to Gitea 28.3.0 or later. As a temporary measure, restrict the creation and use of public-only tokens if not required for your deployment. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119627 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119627?
- 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
Upgrade to Gitea 28.3.0 or later. As a temporary measure, restrict the creation and use of public-only tokens if not required for your deployment.
Technical details
The vulnerability is an authorization bypass in the web profile and RSS/Atom feed routes for users and organizations. When a public-only token authenticated a request via HTTP Basic authentication, the scope restriction was not enforced—only whether a signed-in viewer could access the resource was checked. An attacker with a public-only token can bypass scope checks to read profile pages and activity feeds of limited-visibility accounts, though read-only access to metadata is gained and no write operations are possible.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed