Skip to content
Noroxi
OSV ecosystem advisory

GHSA-rjvx-x5h2-6px5: Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions

Medium—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: code.gitea.io/gitea (Go) 1.26.0.

Low priority for now. Upgrade to code.gitea.io/gitea (Go) 1.26.0 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: OSV

### Summary The API endpoint used to fork repositories into organizations performs a weaker authorization check than the corresponding web UI and other repository creation endpoints. When a repository is forked into an organization through the API, the endpoint only verifies that the user is an organization member (`IsOrgMember()`), but does not verify whether the user is allowed to create repositories in that organization (`CanCreateOrgRepo()`). As a result, organization members belonging to teams with `can_create_org_repo=false` can still create repositories inside the organization by using the fork API. ### Details Affected endpoint: ``` POST /api/v1/repos/{owner}/{repo}/forks ``` In `routers/api/v1/repo/fork.go`, the endpoint performs the following authorization check: ```go if !ctx.Doer.IsAdmin { isMember, err := org.IsOrgMember(ctx, ctx.Doer.ID) if !isMember { ctx.APIError(http.StatusForbidden, ...) return } } ``` The equivalent web UI implementation uses the stronger permission check: ```go isAllowedToFork, err := organization.OrgFromUser(ctxUser). CanCreateOrgRepo(ctx, ctx.Doer.ID) ``` The same `CanCreateOrgRepo()` authorization check is also used by: * CreateOrgRepo API endpoint * GenerateRepository API endpoint The fork endpoint appears to be the only repository creation path that relies solely on organization membership. ### Proof of Concept Tested on Gitea 1.23.7. 1. Create an organization. 2. Create a team with `can_create_org_repo=false`. 3. Add a test user to that team. 4. Verify that normal repository creation is denied: ```http POST /api/v1/orgs/target-org/repos ``` Result: ```http 403 Forbidden ``` 5. Fork a repository into the organization: ```http POST /api/v1/repos/admin/public-repo/forks Content-Type: application/json { "organization": "target-org" } ``` Result: ```http 202 Accepted ``` The repository is successfully created despite repository creation permissions being disabled. ### Impact Users who are organization members but are intentionally prevented from creating repositories can bypass that restriction through the API. This allows unauthorized repository creation inside the organization and may expose additional attack surface depending on the organization's Actions, runner, and workflow configuration. The vulnerability represents an authorization bypass because API behavior is less restrictive than both the web UI and other repository creation endpoints.

Published
Jul 21, 2026
Updated
Jul 27, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

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 GHSA-rjvx-x5h2-6px5

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
Gocode.gitea.io/gitea

Package-level exposure

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

EcosystemPackageAffected rangeFix
Gocode.gitea.io/giteabefore 1.26.01.26.0

Same product

Go: all records

Other highest-scoring records for the same primary product.

  • GO-2026-6074Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions in code.gitea.io/gitea
    0Monitor
  • GO-2026-5091Gitea has insecure default SSH settings in code.gitea.io/gitea
    0Monitor
  • GHSA-3m6q-h5gj-7mrwGitea has insecure default SSH settings
    0Monitor

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.26.0Package 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.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records