Skip to main content
VulnerabilityPublished

CVE-2026-112887: Gitea · Information Exposure

Affects GiteaSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 28.3.0 when convenient.

Data as of 1 Nov 2026, 10:20 UTC

Severity
Medium

Rated Medium 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 github.com/go-gitea/gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • <28.3.0
Fixed in
  • 28.3.0
Gogithub.com/go-gitea/giteapkg:golang/github.com/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 vulnerability is fixed. The fix ensures system users own no repositories and restricts API routes to prevent unauthorized repository enumeration. No additional mitigation is required once the system is updated.

Description

Gitea versions prior to 28.3.0 contain a vulnerability where Actions task tokens authenticate as a shared system user with no owner restrictions, allowing users who can run workflows to list all repositories on the instance, including private ones, via the REST API. Repository contents remain protected by permission checks. The issue is fixed in version 28.3.0 by ensuring system users own no repositories and restricting API routes accordingly.

References

Community reviews

Loading reviews…