Quick answers
- Is CVE-2026-118386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118386 being exploited in the wild.
- How severe is CVE-2026-118386?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea prior to 28.3.0.
- Is there a fix for CVE-2026-118386?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118386 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-118386?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.3.0
Technical details
Review-triggered workflows were executed from the commit specified in the review's `commit_id` field rather than the pull request head, while fork restrictions were evaluated against the pull request itself. An attacker could submit a review naming their own commit on a PR whose head branch is in the same repository, causing workflows to run without approval on untrusted code with access to Actions secrets and a GITEA_TOKEN with repository write permissions. The fix aligns review-triggered workflows with other PR events by executing them on the PR head instead.
Affected products
- Gitea Gitea prior to 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched: Fixed in Gitea 28.3.0