Vulnerability · Published Nov 1, 2026 · Assigned by Gitea

CVE-2026-118386Gitea Actions fork workflow trust through pull request review commit

Unrated

In plain English

A incorrect authorization in Gitea from Gitea. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 4% of all known vulnerabilities).

Severity (CVSS )–Not rated

Exploit odds (30 days)0.1%top 95.9% of all CVEs

Exploited in the wildNo reportsnot in CISA KEV

Attack toolingNoneno public tooling known

Official description

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.

Affected products (as reported)

Vendor	Product	Versions
Gitea	Gitea	1.19.0 – before 28.3.0

Weakness: CWE-863

References

GitHub Security Advisory GHSA-32h8-5xqg-h466 vendor-advisory
Fix: go-gitea/gitea pull request #40099 patch
Fix backport to release/v28: go-gitea/gitea pull request #40117 patch
Gitea 28.3.0 release announcement release-notes
go-gitea/gitea v28.3.0 release release-notes