CVE-2026-58416: Gitea authorization bypass in Actions collaborative-owner access

CVE-2026-58416 · Severity: medium · CVSS 6.3 · Published 2026-07-21

Gitea is a self-hosted Git service used for hosting and managing source code. A vulnerability in its Actions automation system allows an attacker who submits a pull request from a fork to bypass security restrictions and read the contents of other private repositories they should not have access to. This could lead to the exposure of sensitive source code or configuration files stored in private repositories on the same Gitea instance.

Technologies: Gitea, gitea.dev (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-58416 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-58416 being exploited in the wild.
How severe is CVE-2026-58416?
Medium severity, with a CVSS score of 6.3, published 21 July 2026.
Which products and versions are affected?
Gitea < 1.27.0; gitea.dev (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-58416?
Yes. gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58416 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-58416?
Check whether you run Gitea or gitea.dev (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • gitea.dev (Go): upgrade to 1.27.0 or later
    go get gitea.dev@v1.27.0

Technical details

The `GetActionsUserRepoPermission` function in `models/perm/access/repo_permission.go` fails to enforce a fork-PR discriminator in the collaborative-owner logic branch. While other access paths correctly use the `!task.IsForkPullRequest` guard, this specific branch allows an Actions task token generated for a fork PR to inherit code-read permissions for a target private repository if that repository has configured the base repository's owner as a collaborative owner. An attacker with the ability to trigger a workflow (e.g., a previously approved contributor) can use the task token to clone unrelated private repositories via git-HTTP. This is a read-only confidentiality breach fixed in version 1.27.0.

Affected products

  • Gitea Gitea < 1.27.0

Identifiers

  • CVE-2026-58416
  • GHSA-fj8v-hjwv-qm88
  • GO-2026-6052

Timeline

  • 2026-07-13: disclosed: Initial disclosure to vendor
  • 2026-07-21: patched: Fixed in version 1.27.0
  • 2026-07-21: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.