# CVE-2026-63792: Gitea private reusable workflow disclosure to fork runs

> Attackers can read private reusable workflow files from other repositories via fork pull requests in Gitea when collaborative-owner trust is configured.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-2xph-7j4g-43rg

## What is CVE-2026-63792?

CVE-2026-63792 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository that trusts the base repository's owner through collaborative-owner configuration. The issue exposes private reusable workflow contents at caller-selected Git refs; it does not itself grant write access or code execution in the other repository.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2026-63792?


## How do I fix CVE-2026-63792?

No fix has been published for CVE-2026-63792 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63792 being exploited?

There is no known exploitation of CVE-2026-63792 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63792 and fix it if it is affected.

What it is: CVE-2026-63792 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63792 in the wild and no public exploit code.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63792/ (Markdown: https://insights.sbomify.com/CVE-2026-63792/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63792
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63792
- OSV: https://osv.dev/vulnerability/CVE-2026-63792

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63792/
Summaries are generated and may contain mistakes; the official description above is the record.