CVE-2026-70396 Gitea CVE debrief

Who should care

Gitea administrators and users with organization repository creation enabled should assess exposure and verify token scopes. Defenders should prioritize verifying Gitea deployments, especially those with organization repository creation enabled, and ensure tokens are properly scoped.

Why it matters

The CVE-2026-70396 vulnerability in Gitea's organization repository creation API allows unauthorized repository creation, requiring defenders to verify token scopes and user permissions.

• Repository creation without proper token scope can lead to unauthorized repository creation
• Defenders need to verify token scopes to prevent exploitation
• Gitea deployments with organization repository creation enabled require immediate attention

Technical summary

The vulnerability allows creation of organization-owned repositories using a personal access token or OAuth application token without repository-write scope, if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions. Defenders should prioritize verifying Gitea deployments, especially those with organization repository creation enabled, and ensure tokens are properly scoped. The CVE record and source item provide details on the token scope bypass vulnerability in Gitea's organization repository creation API.

Defensive priority

Defenders should prioritize verifying Gitea deployments, especially those with organization repository creation enabled, and ensure tokens are properly scoped.

Recommended defensive actions

• Verify Gitea deployments for organization repository creation enabled
• Ensure tokens are properly scoped for repository creation
• Review user permissions and access controls
• 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
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and source item provide details on the token scope bypass vulnerability in Gitea's organization repository creation API. The vulnerability allows creation of organization-owned repositories using a personal access token or OAuth application token without repository-write scope, if the authorizing user has permission to do so. Defenders should verify token scopes to prevent exploitation. Gitea deployments with organization repository creation enabled require immediate attention.

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.