CVE-2026-34966
Authenticated SSRF in Gitea allows access to internal services and local files.
Is CVE-2026-34966 being exploited?
Not confirmed. CVE-2026-34966 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-34966?
CVE-2026-34966 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34966?
Yes. A fix has been recorded for CVE-2026-34966. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34966 affect?
CVE-2026-34966 affects Gitea < 1.27.0, self-hosted Gitea instances, migration release asset fetchers, OAuth avatar and PR patch fetchers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34966?
Upgrade Gitea to 1.27.0 immediately; block metadata endpoints and restrict outbound fetches.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can perform SSRF to access internal/cloud metadata, read config files (DB creds, signing secrets) and exfiltrate via release assets.
Immediate action required
- affected<= 1.26.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.