Gitea · Gitea · published 2026-10-06

CVE-2026-89430Gitea push mirror SSRF and forced writes to internal Git hosts

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-89430 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 8.1 (v3.1), a successful attack gives total control of the component. 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% (19th pct)FIRST EPSS v2026.06.15
CVSS base score8.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to `git push`, so a name that later resolved to a blocked or internal address was still reached. A user with administrator access to a repository, which includes repositories they create themselves, could aim push mirror synchronization at internal Git services and force-push the repository's contents to them.

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 →