Gitea · Gitea · published 2026-10-14

CVE-2026-71184Gitea fork workflow approval bypass through review events

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-71184 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This Gitea vulnerability: CVSS 8.8 (v3.1), a successful attack gives total control of the component. 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.5% (43th pct)FIRST EPSS v2026.06.15
CVSS base score8.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code from the fork head and run it on the base repository's runners without the required maintainer approval. This allows execution of fork-controlled workflow code across the intended approval boundary.

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 →