Skip to main content
VulnerabilityPublished

CVE-2026-116289: 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 and go-gitea/gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • <28.3.0
Fixed in
  • 28.3.0
GitHubgo-gitea/giteapkg:github/go-gitea/giteaOther threatsAffected
  • <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 this authorization issue is fixed. No other mitigation is indicated.

Description

Gitea versions prior to 28.3.0 contain an authorization flaw where personal access tokens restricted to public resources can be used to register organization-level runners that access private repository workflows, secrets, and variables. This vulnerability allows an attacker with a token having write:organization scope from a public organization owner to gain unintended access to private repository jobs. The issue is fixed in version 28.3.0.

References

Community reviews

Loading reviews…