Gitea · Gitea · published 2026-10-06

CVE-2026-89182Gitea push-to-create bypass of FORCE_PRIVATE policy

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-89182 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This Gitea vulnerability: CVSS 5.4 (v3.1). Fixed upstream in Gitea 28.1.0, 28.0.0. Patch in your normal monthly cycle.

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.2% (10th 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:L/I:L/A:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.

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 →