ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-34966

Gitea: SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata

Published Jul 21, 2026 · catalog updated Oct 14, 2026 · Gitea: SSRF via Migration

Check if you run it

No confirmed exploitation is on record for CVE-2026-34966. EPSS is 0.39%. Act only if a listed version of Gitea: SSRF via Migration is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Gitea: SSRF via Migration).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Advisory link
Affected products
Go code.gitea.io/gitea · Go gitea.dev

### Summary Gitea has robust SSRF protection via for webhook and migration clone URLs, which validates resolved IPs at the TCP dial level. However, three code paths use raw (Go's ) which completely bypasses this protection, enabling SSRF to internal services and local file read via the scheme. ### Vulnerable Code **File: (line 32) -- Core vulnerability** **Callers in migration path:** - -- for release assets - -- for PR patches **File: (lines 312, 453)** **File: (line 306)** **Contrast with protected migration clone (same codebase):** ### PoC ### Impact - **Cloud metadata theft:** reachable via unfiltered (AWS IMDSv1 credentials, GCP tokens) - **Local file read:** scheme in reads (database credentials, JWT signing secrets, SMTP passwords) - **Internal service scanning:** Reach , , , networks - **Bypasses existing SSRF protection:** The dialer is comprehensive but only applied to webhook and clone transports -- these three paths are unprotected - Migration vectors require migration permission (admin/org owner); OAuth vector requires admin-configured custom OAuth2 source

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go code.gitea.io/gitea0 → 1.27.0
  • Go gitea.dev0 → 1.27.0

How to fix CVE-2026-34966

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-34966. EPSS is 0.39%. Act only if a listed version of Gitea: SSRF via Migration is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.27.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 21, 2026 · GitHub Advisory Database

    Detected

    ### Summary Gitea has robust SSRF protection via for webhook and migration clone URLs, which validates resolved IPs at the TCP dial level. However, three code paths use raw (Go's ) which completely bypasses this protection, enabling SSRF to internal services and local file read via the scheme. ### Vulnerable Code **File: (line 32) -- Core vulnerability** **Callers in migration path:** - -- for rel

  2. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    code.gitea.io/gitea fixed in 1.27.0; gitea.dev fixed in 1.27.0

  3. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    code.gitea.io/gitea fixed in 1.27.0

  4. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea.dev fixed in 1.27.0

  5. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea.dev fixed in 1.27.0

  6. Oct 14, 2026 · GitHub Advisory Database

    Updated

    ### Summary Gitea has robust SSRF protection via for webhook and migration clone URLs, which validates resolved IPs at the TCP dial level. However, three code paths use raw (Go's ) which completely bypasses this protection, enabling SSRF to internal services and local file read via the scheme. ### Vulnerable Code **File: (line 32) -- Core vulnerability** **Callers in migration path:** - -- for rel

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.