CVE.org (no NVD analysis yet)· CNA Gitea

CVE-2026-104636: Gitea SSRF through Git HTTP redirects in mirrors and fetches

HighCVSS 7.5 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
No fixed version is recorded, but the references include a patch (commit or PR) link.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

EUVD-2026-93916

Published: Oct 6, 2026
Updated: Oct 13, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-918

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gitea	gitea	cpe:2.3:a:gitea:gitea

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.

Gitea Gitea
- up to and including 1.27.3affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gitea giteabefore 28.0.0

Same product

gitea: all records

Other highest-scoring records for the same primary product.

CVE-2026-60004Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.KEV
76This week
CVE-2026-59774Gitea Org-mode file disclosure and code execution
60This week
CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.
60This week

Published before and after this one in the same product

← EarlierCVE-2026-104626Oct 6, 2026 · Gitea fork workflow job revival through later approval
35Monitor
← EarlierCVE-2026-104632Oct 6, 2026 · Gitea fork workflow approval bypass through cancel and rerun
35Monitor
Later →CVE-2026-70357Oct 6, 2026 · Gitea repository migration SSRF through DNS rebinding
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

go-gitea/giteaPR 39426

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

https://github.com/ihopenre-engreporter
https://github.com/ElectQreporter
https://github.com/TheFox0x7remediation developer
https://github.com/silverwindremediation developer
https://github.com/bircniremediation developer
https://github.com/wxiaoguangremediation developer

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-3496662 days apartGitea prior to 1.27.0 SSRF via Migration URI Fetch Bypass
33Monitor
CVE-2026-703570 days apartGitea repository migration SSRF through DNS rebinding
30Monitor
CVE-2026-259468 days apartGitea OpenID discovery server-side request forgery
21Monitor
CVE-2026-782318 days apartGitea blind SSRF through OpenID assertion verification
21Monitor
CVE-2026-964000 days apartGitea migration SSRF to reserved addresses through ALLOWED_DOMAINS
17Monitor