CVE-2026-118386
Gitea Actions fork workflow trust through pull request review commit
Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: GiteaFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: GiteaFix
gitea.dev (go): GitHub reports patched versions 28.3.0. Check the advisory for the affected release branch.
Source: GitHub GHSA-32h8-5xqg-h466Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Gitea Gitea gitea.dev
|
≥ 1.19.0; < 28.3.0 (affected, semver)
Other versions: unaffected |
CNA: Gitea |
gitea.devgitea.dev
go |
>= 1.19.0, <= 28.2.0 (affected, GitHub advisory range) | GitHub GHSA-32h8-5xqg-h466 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 6.5 medium |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | ADP: CISA-ADP |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h466CNA: Gitea · vendor-advisory
- https://github.com/go-gitea/gitea/pull/40099CNA: Gitea · patch
- https://github.com/go-gitea/gitea/pull/40117CNA: Gitea · patch
- https://blog.gitea.com/release-of-28.3.0/CNA: Gitea · release-notes
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0CNA: Gitea · release-notes
- https://blog.gitea.com/release-of-28.3.0/88ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/pull/4009988ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/pull/4011788ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/releases/tag/v28.3.088ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h46688ee5874-cf24-4952-aea0-31affedb7ff2
- https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h466GitHub Security Advisories · advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.