CVE-2026-71184 Gitea CVE debrief

Who should care

Gitea instance administrators and maintainers should assess exposure and verify the impact of this vulnerability on their instances, especially those with public or untrusted forks. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their Gitea instances. Gitea instance administrators and maintainers should review and update Gitea instances to version 1.27.3 or later and monitor Gitea instance logs for and G.

Why it matters

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their Gitea instances, especially those with public or untrusted forks.

• Execution of fork-controlled workflow code across the intended approval boundary
• Potential for unauthorized code execution on Gitea instances
• Need for verification of Gitea instance exposure and impact

Technical summary

The Gitea pull request review notifier does not attach the pull request to the Actions notification, allowing execution of fork-controlled workflow code across the intended approval boundary. This allows attackers to run workflow code from the fork head on the base repository's runners without the required maintainer approval. Gitea instance administrators and maintainers should assess exposure and verify the impact of this vulnerability on their instances, especially those with public or untrusted forks. The vulnerability affects Gitea instances with public or untrusted forks.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their Gitea instances, especially those with public or untrusted forks.

Recommended defensive actions

• Verify Gitea instance exposure and assess the impact of this vulnerability
• Review and update Gitea instances to version 1.27.3 or later
• Monitor Gitea instance logs for suspicious activity
• 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, but limited information is available on exploitation or affected versions. Defenders should verify Gitea instance exposure and assess the impact of this vulnerability, especially those with public or untrusted forks. The Gitea pull request review notifier does not attach the pull request to the Actions notification, allowing execution of fork-controlled workflow code across the intended approval boundary.

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.