Gitea · Gitea · published 2026-10-06

CVE-2026-79960Gitea deploy key pushes acting as the repository owner

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-79960 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 11% of all CVEs. This Gitea vulnerability: CVSS 7.1 (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.2% (12th pct)FIRST EPSS v2026.06.15
CVSS base score7.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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)#

When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.

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 →