CVE-2026-118386

medium

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.

References

https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h466

https://github.com/go-gitea/gitea/releases/tag/v28.3.0

https://github.com/go-gitea/gitea/pull/40117

https://github.com/go-gitea/gitea/pull/40099

https://blog.gitea.com/release-of-28.3.0/

Details

Source: Mitre, NVD

Published: 2026-11-01

Updated: 2026-11-01

Risk Information

CVSS v2

Base Score: 4

Vector: CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N

Severity: Medium

CVSS v3

Base Score: 6.5

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Severity: Medium

EPSS

EPSS: 0.00198