ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-104636

Gitea SSRF through Git HTTP redirects in mirrors and fetches

Published Oct 14, 2026 · catalog updated Oct 14, 2026 · Gitea SSRF through Git

Check if you run it

No confirmed exploitation is on record for CVE-2026-104636. EPSS is 0.26%. Act only if a listed version of Gitea SSRF through Git is installed.

Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.26%
Remediation
Advisory link
Affected products
Bitnami gitea

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.

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.

  • Bitnami gitea0 → 28.0.0

How to fix CVE-2026-104636

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-104636. EPSS is 0.26%. Act only if a listed version of Gitea SSRF through Git is installed.

Which versions are affected?

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

What should an analyst verify?

No weakness class is stored. EPSS 0.26%. 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. 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

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.