Skip to main content
VulnerabilityPublished

CVE-2026-118504: Gitea issue changes on archived repositories through the API

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:07 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 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 the issue is fully fixed by enforcing archived repository checks on all modifying API requests. No additional mitigation is required once updated.

Description

Gitea versions prior to 28.3.0 allowed users with permission to modify issues on archived repositories via the REST API, bypassing the web interface restriction that prevents changes on archived repositories. This could lead to unauthorized edits, closures, deletions, label changes, time tracking modifications, reactions, issue block changes, and pinning of issues in archived repositories. The issue was fixed in version 28.3.0 by applying the archived repository check to all modifying API requests.

References

Community reviews

Loading reviews…