# CVE-2026-73800: Gitea reusable workflow secret exposure in pull_request_target

> Attackers can execute arbitrary code and access secrets by modifying reusable workflows in forks when pull_request_target events are used.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Oct 2026
- **Also known as:** GHSA-r9ch-mqjm-g67v

## What is CVE-2026-73800?

CVE-2026-73800 is a high-severity code injection 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 resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to that event. Exploitation requires a base workflow that calls a local reusable workflow, and bypasses the intended separation between trusted base code and untrusted fork code.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-73800 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73800 is a high-severity code injection 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-73800 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-73800/ (Markdown: https://insights.sbomify.com/CVE-2026-73800/index.md)
```

## Sources

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

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