CVE-2026-20750
Gitea broken access control
- Published22 Jan 2026
Description
Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-20750
- https://blog.gitea.com/release-of-1.25.4/
- https://bugzilla.redhat.com/show_bug.cgi?id=2432216
- https://github.com/go-gitea/gitea/pull/36318
- https://github.com/go-gitea/gitea/pull/36373
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4
- https://github.com/go-gitea/gitea/security/advisories/GHSA-h4fh-pc4w-8w27
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-20750.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-20750 being actively exploited?
CVE-2026-20750 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.44%.
How severe is CVE-2026-20750?
CVE-2026-20750 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.44% probability of exploitation.
Which products are affected by CVE-2026-20750?
Affected products include Gitea.
How do I fix CVE-2026-20750?
Upgrade affected software to a fixed version, for example Gitea 1.25.4 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-20750 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.