Skip to main content
VulnerabilityPublished

CVE-2026-58416: Gitea · Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)

Affects gitea.devSource GCVE Database

0
Compare
Authoritative record:CVE-2026-58416· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.27.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.27.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade gitea.dev to 1.27.0.

Affected software

ProductAffectedFixed in
Gogitea.devAffected
  • <1.27.0
Fixed in
  • 1.27.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Gitea version 1.27.0 that fixes this vulnerability by adding the missing permission guard against fork pull-requests in the collaborative-owner branch. Users should upgrade to version 1.27.0 or later to remediate this issue.

Description

Gitea versions prior to 1.27.0 contain a vulnerability where a fork pull-request Actions workflow can read a third private repository if that repository trusts the fork's base repository owner as a collaborative owner. This occurs due to a missing permission guard against fork pull-requests in the collaborative-owner branch, resulting in unauthorized read access. The vulnerability leads to a confidentiality breach exposing the full source code of a private repository to an untrusted fork PR author. A patch is available to address this issue.

References

Community reviews

Loading reviews…