CVE-2026-73800 json
Gitea reusable workflow secret exposure in pull_request_target
published 2mo ago modified 24d ago also EUVD-2026-101106 , GHSA-r9ch-mqjm-g67v
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Gitea Gitea 1.27.2
- github.com/go-gitea/gitea#38886 pull request
- github.com/go-gitea/gitea#38897 pull request
- github.com/go-gitea/gitea/releases/tag/v1.27.2 release
Is CVE-2026-73800 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-73800 updated cvss 8.8
code.gitea.io/gitea: Gitea: arbitrary code execution via untrusted reusable workflow resolution
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 24d ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Gitea Gitea
Classification
References
-
github.com
/go-gitea/gitea/pull/38886
patch
-
github.com
/go-gitea/gitea/pull/38897
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-r9ch-mqjm-g67v
vendor-advisory, advisory
-
blog.gitea.com
/release-of-1.27.2/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v1.27.2
release-notes
Sources
- CVE List CVE-2026-73800
- NVD CVE-2026-73800
- Maintainer advisory GHSA-r9ch-mqjm-g67v
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.