Gitea · Gitea · published 2026-10-06

CVE-2026-97208Gitea push mirror API bypass of DISABLE_NEW_PUSH policy

Routine No exploitation evidence; EPSS 0.3%.

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

Share this

Remediation#

Fixed upstream in Gitea 28.1.0, 28.0.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security releases: 28.1.0, 28.0.0

    Upgrade to 28.1.028.0.0

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

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (18th pct)FIRST EPSS v2026.06.15
CVSS base score4.9 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:H/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 Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.

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 →