Gitea · Gitea · published 2026-11-01

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

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-118504 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 27% of all CVEs. This Gitea vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Gitea 28.3.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Gitea 28.3.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security release: 28.3.0

    Upgrade to 28.3.0

    Why: Vendor security release for server software (most severe: CVE-2026-120263).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (27th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and deadlines, add or delete tracked time and stopwatches, add reactions, change issue blocks, and pin issues, altering data that archiving is meant to freeze. Gitea 28.2.0 added the check to the issue edit, delete and label routes; Gitea 28.3.0 applies it to all modifying repository API requests.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →