Skip to main content
VulnerabilityPublished

CVE-2026-119441: Gitea · Incorrect Authorization

Affects GiteaSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 28.3.0 soon.

Data as of 1 Nov 2026, 10:07 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 28.3.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade Gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • >=1.27.0 <28.3.0
Fixed in
  • 28.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Gitea to version 28.3.0 or later, where the authorization checks have been corrected to reject public-only tokens on organization ownership routes. This update prevents public-only tokens from deleting private repositories. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-119441 is an authorization vulnerability in Gitea affecting versions from 1.27.0 up to but not including 28.3.0. The DELETE API endpoint for deleting all repositories of an organization did not properly enforce restrictions on public-only access tokens. This allowed a public-only token belonging to an owner of a public organization to delete private repositories within that organization, which should have been inaccessible with such a token. The issue has been fixed in version 28.3.0 by rejecting public-only tokens on routes requiring organization ownership.

References

Community reviews

Loading reviews…