GO · JULY 2026 · EARLY WARNING

Gitea Local File Inclusion Vulnerability Under Investigation

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-5GGR-2F2H-JMVMSeverity: HIGH

Gitea's restore-repo command is reportedly vulnerable to local file inclusion via file:// URI, potentially allowing arbitrary file exfiltration.

What happened

Gitea's restore-repo command processes release.yml files from user-supplied archives. The DownloadURL field in each release attachment is passed to uri.Open() without scheme validation. This appears to allow an attacker to exfiltrate arbitrary files from the server filesystem using a file:// URI.

The vulnerability affects go-gitea/gitea versions up to and including v1.22.x, as well as the master branch as of the latest commit. The issue is tracked under GHSA-5GGR-2F2H-JMVM.

It is recommended to upgrade to a version of Gitea that includes the fix for this vulnerability and review any release attachments for unauthorized content. For more details, consult the primary source at https://github.com/go-gitea/gitea/security/advisories/GHSA-5ggr-2f2h-jmvm.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If go-gitea/gitea is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats