Skip to content
Noroxi
NVD / CVE Program· CNA Gitea

CVE-2026-20750: Gitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: code.gitea.io/gitea (Go) 1.25.4; github.com/go-gitea/gitea (Go) 1.25.4.

Low priority for now. Upgrade to code.gitea.io/gitea (Go) 1.25.4; github.com/go-gitea/gitea (Go) 1.25.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jan 22, 2026
Updated
Jul 15, 2026
EPSS
0.4% · 37th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-20750

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
giteagitea

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.

  • Gitea Gitea Open Source Git Server

    • up to and including 1.25.3affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gitea giteabefore 1.25.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gocode.gitea.io/giteabefore 1.25.41.25.4
Gogithub.com/go-gitea/giteabefore 1.25.41.25.4

Other highest-scoring records for the same primary product.

  • CVE-2026-60004Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.KEV
    76This week
  • CVE-2026-59774Gitea Org-mode file disclosure and code execution
    60This week
  • CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2026-0798Jan 22, 2026 · Gitea Release Email Notifications Leak Private Repository Release Details After Access Revocation
    14Monitor
  • ← EarlierCVE-2026-20736Jan 22, 2026 · Gitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership Check
    30Monitor
  • Later →CVE-2026-20800Jan 22, 2026 · Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:code.gitea.io/gitea1.25.4Package registry (OSV)
Go:github.com/go-gitea/gitea1.25.4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-208970 days apartGitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)
    36Monitor
  • CVE-2026-209120 days apartGitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure
    36Monitor
  • CVE-2026-66877265 days apartGitea fork workflow approval bypass through concurrency cancellation
    32Monitor
  • CVE-2026-207360 days apartGitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership Check
    30Monitor
  • CVE-2026-118395283 days apartGitea public-only token bypass in repository and organization creation
    30Monitor
  • CVE-2026-208830 days apartGitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure
    26Monitor

Not on record for this CVE: EPSS history · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

References

All records