ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-94205

Gitea fork workflow approval bypass through maintainer-triggered events

Published Oct 14, 2026 · catalog updated Oct 14, 2026 · Gitea fork workflow approval

Check if you run it

No confirmed exploitation is on record for CVE-2026-94205. EPSS is 0.36%. Act only if a listed version of Gitea fork workflow approval is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Gitea fork workflow approval).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.36%
Remediation
Advisory link
Affected products
Bitnami gitea

Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Bitnami gitea0 → 28.0.0

How to fix CVE-2026-94205

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-94205. EPSS is 0.36%. Act only if a listed version of Gitea fork workflow approval is installed.

Which versions are affected?

Compare what you have installed with 0 → 28.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.36%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · GitHub Advisory Database

    Detected

    Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is

  2. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.0.0

  3. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.0.0

  4. Oct 14, 2026 · GitHub Advisory Database

    Updated

    Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.