cve.bz

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

9.1 criticalEPSS 0.6%Fix available

Critical (9.1) in gitea gitea open source git server. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in code.gitea.io/gitea 1.27.0.

On this page
Public-only repository tokens can update private PR head branches

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
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-58443 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-58443?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-58443?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-58443 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-xxjv-752h-3vp2Gocode.gitea.io/gitea<1.27.01.27.0
GO-2026-6086Gogitea.dev<1.27.01.27.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260727T201416-160000.1.1SUSE-SU-2026:23216-1 SUSE-SU-2026:23227-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260727T201416-160000.1.1openSUSE-SU-2026:21551-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: SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in Gitea where public-only repository tokens can be used to write to private pull request head branches. This authorization bypass allows an attacker with a valid public-only write:repository token to modify private repository branches through public base repository API endpoints, bypassing the public-only token restriction. This could lead to unauthorized changes in private code, compromising the integrity of affected repositories and potentially triggering private workflow executions when Actions is enabled.

Red Hat's mitigation

Update to Gitea 1.27.0 or later. As a workaround, restrict the use of public-only tokens in environments where both public and private repositories with pull request relationships exist, or implement additional access controls at the API gateway level to prevent access to pull request update endpoints.

ProductPackageStateAdvisory
OpenShift Pipelinesopenshift-pipelines-clientWill not fix

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-58443.

References

Check your stackJSON