Gitea · Gitea · published 2026-10-14

CVE-2026-70400Gitea private migration creation with public-only tokens

Routine No exploitation evidence; EPSS 0.4%.

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

Share this

Remediation#

Fixed upstream in Gitea 1.27.3.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security release: 1.27.3

    Upgrade to 1.27.3

    Why: CVE-2026-73504: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

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

Affected versions (from the CVE record)#

Description (from the CVE record)#

Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing account or an organization where that user has the necessary permissions. The ordinary private repository-creation route rejects the same token, but the migration path omits that restriction.

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 →