CVE-2026-59765: SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata
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.37% (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.
- Fixed version: code.gitea.io/gitea (Go) 1.27.0; gitea.dev (Go) 1.27.0.
Low priority for now. Upgrade to code.gitea.io/gitea (Go) 1.27.0; gitea.dev (Go) 1.27.0 or later.
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
- Published
- Aug 13, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-918
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- 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
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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 Open Source Git Server
- up to and including 1.26.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | code.gitea.io/gitea | before 1.27.0 | 1.27.0 |
| Go | gitea.dev | before 1.27.0 | 1.27.0 |
Same product
gitea: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-6886Inproper Sanitation of field leading to stored XSS50Plan
- CVE-2026-20896Gitea Docker image trusts spoofable reverse-proxy headers by default40Plan
- CVE-2026-56654Privilege Escalation via Access Token Scope Escalation in API39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-58510Aug 13, 2026 · GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private17Monitor
- ← EarlierCVE-2026-58511Aug 13, 2026 · Webhook Authorization Header Returned in Plaintext via API10Monitor
- ← EarlierCVE-2026-59763Aug 13, 2026 · Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:code.gitea.io/gitea | 1.27.0 | Package registry (OSV) |
| Go:gitea.dev | 1.27.0 | Package registry (OSV) |
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.
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.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Letian-aarch64reporter
- tikket1reporter
- theluckystrikereporter
- JebeenLeereporter
- JLLeitschuhreporter
- pickreporter
- noobx123reporter
- kdalal-vulncheckcoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2287441 days apartGitea webhook and migration allow-list filtering permits SSRF38Monitor
- CVE-2026-578940 days apartRepository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration34Monitor
- CVE-2026-583140 days apartTwo SSRF findings in Gitea 1.26.230Monitor
- CVE-2026-5841841 days apartSSRF via HTTP Redirect in Repository Migration26Monitor
- CVE-2026-584410 days apartSSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL25Monitor
- CVE-2026-236030 days apartBlind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim12Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- 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.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.