ZeroDay Findings
Sign inSign up

Findings

CVE-2026-104636

Gitea SSRF through Git HTTP redirects in mirrors and fetches

Published Oct 14, 2026 · updated Oct 14, 2026

Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint that redirects could make Gitea's Git client send requests to an address that the outbound host policy would otherwise block. The impact depends on the configured policy and the internal services reachable from the server.

Code

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

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · GitHub Advisory Database

    Detected

    Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint that redirects could make Gitea's Git client send requests to an address that the outbound host policy would otherwise b

  2. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.0.0

  3. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.0.0

  4. Oct 14, 2026 · GitHub Advisory Database

    Updated

    Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint that redirects could make Gitea's Git client send requests to an address that the outbound host policy would otherwise b

Affected

  • Bitnami gitea0 → 28.0.0

Sources

References