cve.bz

CVE-2026-58416 gitea gitea open source git server: Incorrect Authorization

7.1 highEPSS 0.3%Fix available

High (7.1) in gitea gitea open source git server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in gitea.dev 1.27.0.

On this page
Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-280 Improper Handling of Insufficient Permissions or Privileges
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-58416 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-58416?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-58416?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-58416 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Gitea Open Source Git Serverthrough 1.26.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fj8v-hjwv-qm88Gogitea.dev<1.27.01.27.0
GO-2026-6052Gogitea.dev<1.27.01.27.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Gitea's Actions continuous integration runner logic for pull requests from forked repositories. Due to a missing permission boundary check on collaborative-owner branches, a Gitea Actions workflow triggered by a fork pull request can access unauthorized repository contexts. An authenticated remote user with write access to a fork can exploit this vulnerability to read sensitive data and configuration secrets from a third private repository accessible to the collaborative owner.

Red Hat's mitigation

To mitigate this issue, repository administrators should disable Gitea Actions on affected repositories or restrict pull request workflows from fork repositories by configuring `RUN_WORKFLOWS_FROM_FORK_PULL_REQUESTS` to `false` in the Gitea configuration.

ProductPackageStateAdvisory
OpenShift Pipelinesopenshift-pipelines/pipelines-pipelines-as-code-watcher-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-58416.

References

Check your stackJSON