CVE-2026-94205 Gitea CVE debrief

Who should care

Defenders responsible for Gitea instances, especially those where maintainers frequently interact with pull requests from forks, should assess their exposure to this vulnerability and take steps to mitigate it.

Why it matters

Defenders should prioritize verifying their Gitea instances for exposure and update their workflow configurations to prevent potential unauthorized workflow execution.

• Potential unauthorized workflow execution on the base repository's runners.
• Possible exposure of Gitea instances to malicious workflow code.

Technical summary

The vulnerability occurs when a maintainer triggers certain events, such as adding a label to a pull request, which can cause a workflow run to be created without requiring approval. The workflow definition is taken from the fork head, potentially allowing fork-controlled workflow code to run on the base repository's runners. This issue arises in Gitea instances where Actions are enabled and a matching runner is registered. Defenders should prioritize verifying their Gitea instances for exposure, especially if maintainers frequently interact with pull requests from forks. They should also review and update their workflow configurations to ensure proper approval requirements are in place.

Defensive priority

Defenders should prioritize verifying their Gitea instances for exposure, especially if maintainers frequently interact with pull requests from forks. They should also review and update their workflow configurations to ensure proper approval requirements are in place.

Recommended defensive actions

• Verify Gitea instances for exposure, especially if maintainers frequently interact with pull requests from forks.
• Review and update workflow configurations to ensure proper approval requirements are in place.
• Apply the patch provided by Gitea to fix the issue.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, the CVSS score and severity are not provided. The vendor, Gitea, has released an advisory and a patch for the issue.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.