Quick answers
- Is CVE-2026-116474 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116474 being exploited in the wild.
- How severe is CVE-2026-116474?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-116474?
- Yes: fixed in Gitea 28.3.0. Until then: Restrict who can create and run workflow jobs in your Gitea instance, as the vulnerability requires the ability to execute Actions workflows. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116474 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116474?
- 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
Restrict who can create and run workflow jobs in your Gitea instance, as the vulnerability requires the ability to execute Actions workflows.
Technical details
A Gitea Actions job's GITEA_TOKEN authenticated as the `gitea-actions` system user and was accepted by the `/api/v1/user` email and GPG key endpoints without email confirmation. When a GPG key without a real owner is registered, Gitea treats it as the instance's signing key, so any commit signed with that attacker-controlled key displays as verified by the instance. The vulnerability requires the ability to run a workflow job and affects commit signature verification display only; signature enforcement mechanisms remain unaffected.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched