CVE-2026-70400 Gitea CVE debrief

Who should care

Gitea administrators and users with repository creation permissions should assess exposure to public migration tokens and verify the impact of potential unauthorized private repository creation.

Why it matters

Defenders should care about CVE-2026-70400 because it allows unauthorized creation of private repositories using public-only tokens, potentially exposing Gitea instances to security risks. Gitea administrators and users with repository creation permissions should assess exposure and verify the impact of potential unauthorized private repository creation. The issue requires verification from official sources, and remediation involves updating Gitea to version 1.27.3 or later.

• Potential unauthorized creation of private repositories
• Possible exposure of Gitea instances to public migration tokens
• Need for verification of Gitea instance configuration and token usage
• Potential impact on repository security and access control

Technical summary

The Gitea repository migration API does not properly validate tokens when creating a private repository migration, allowing a public-only token to create a private repository and migration task. This issue affects Gitea versions up to 1.27.2 and enables unauthorized creation of private repositories, potentially exposing Gitea instances to security risks. The vulnerability requires verification from official sources, and remediation involves updating Gitea to version 1.27.3 or later. The CVE Program record and NIST NVD detail page offer additional

Defensive priority

Defenders should prioritize verifying exposure of Gitea instances to public migration tokens and assess the impact of potential unauthorized private repository creation.

Recommended defensive actions

• Verify Gitea instance exposure to public migration tokens
• Assess the impact of potential unauthorized private repository creation
• Update Gitea to version 1.27.3 or later
• 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. The issue is related to Gitea's repository migration API, which does not properly validate tokens when creating a private repository migration. This allows a public-only token to create a private repository and migration task. The CVE Program record and NIST NVD detail page offer additional information on the vulnerability. The vendor advisory and release notes for Gitea 1.27.3 provide guidance on remediation. Evidence

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.