CVSS 3.1
9.1 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HCritical (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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:Hcode.gitea.io/gitea (Go): fixed in 1.27.0gitea.dev (Go): fixed in 1.27.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Gitea Open Source Git Server | through 1.26.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-xxjv-752h-3vp2 | Go | code.gitea.io/gitea | <1.27.0 | 1.27.0 |
| GO-2026-6086 | Go | gitea.dev | <1.27.0 | 1.27.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 | SUSE-SU-2026:23216-1 SUSE-SU-2026:23227-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260727T201416-160000.1.1 | openSUSE-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift Pipelines | openshift-pipelines-client | Will 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.