CVE-2026-60021 Gitea CVE debrief

Who should care

Defenders responsible for Gitea instances, especially those using the GitLab migration feature, should assess their exposure to this vulnerability and prioritize remediation efforts accordingly.

Why it matters

This vulnerability allows an authenticated user to cause a denial-of-service attack on Gitea instances using the GitLab migration feature. Defenders should prioritize verifying exposure, assessing impact, and implementing compensating controls or patches to mitigate the vulnerability.

• Denial of service: An attacker can cause the migration worker pool to be exhausted, preventing other migrations from progressing.
• Verification priority: Defenders need to verify if their Gitea instance is exposed to this vulnerability and assess the impact on their system.

Technical summary

The vulnerability exists in Gitea's GitLab migration feature, where an authenticated user can cause a migration task to target an attacker-controlled server. This can lead to a denial-of-service attack, exhausting the migration worker pool and preventing other migrations from progressing. The vulnerability is caused by the use of an HTTP client without a timeout and failure to attach the migration task's cancellation context. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if they use Gitea's GitLab migration feature.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially if they use Gitea's GitLab migration feature.

Recommended defensive actions

• Verify if the Gitea instance is exposed to this vulnerability by checking the version and ensuring it is not using an affected version.
• Assess the impact of this vulnerability on the system and prioritize remediation efforts accordingly.
• Implement compensating controls, such as monitoring and exception tracking, to detect and respond to potential attacks.
• Consider applying the patches provided by the vendor to fix the vulnerability.
• Review 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 about the vulnerability, including its description and affected versions. However, the CVSS score and severity are not provided. The vulnerability is confirmed to exist in Gitea's GitLab migration feature. Defenders should verify if their Gitea instance is exposed to this vulnerability by checking the version and ensuring it is not using an affected version. The CVE Program record and NVD detail page provide additional information about the vulnerability.

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.