CVE-2026-34966
HighCVSS 7.6Exploitation Probability (EPSS)
Low risk24th percentile - higher than 24% of all known CVEs
Summary
Gitea prior to 1.27.0 contains a Server-Side Request Forgery (SSRF) vulnerability allowing authenticated attackers to bypass SSRF protections and access internal services, cloud instance metadata endpoints, or read local files such as application configuration with database credentials and signing secrets. Attackers can exploit HTTP fetch operations in migration and OAuth avatar code paths.
Risk Assessment
An attacker can access sensitive internal data, including database credentials and secrets, potentially leading to full system compromise. Data can be exfiltrated via migration assets.
Recommendation
Upgrade Gitea to version 1.27.0 or later. Restrict access to internal services and monitor migration operations.
Other vulnerabilities in Gitea
See all- CVE-2026-60004CriticalActively exploited
Gitea before version 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
- CVE-2026-58508Critical
Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation).
- CVE-2026-58443Critical
Public-only repository tokens can update private PR head branches.
- CVE-2026-58433Critical
The team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting. This means a user without proper permissions can change repository-team assignments.
- CVE-2026-56750Critical
Theft of the Remember-Me token in Gitea does not invalidate the attacker's session, allowing continued unauthorized access.
- CVE-2026-56654Critical
The vulnerability allows privilege escalation via access token scope escalation in the API.
- CVE-2026-56443Critical
A public-only scope token can bypass restrictions on limited-visibility owners (Repository and Package categories) — residual after CVE-2026-25714 / PR #37118.
- CVE-2026-55982Critical
The OIDC userinfo endpoint returns identity claims without enforcing API token scopes.
- CVE-2026-58426Critical
The vulnerability in Gitea Actions Artifacts V4 stems from HMAC ambiguity in signed URLs, allowing cross-repository artifact read and cross-task upload-state write.
- CVE-2026-27780Critical
A vulnerability in Gitea before version 1.26.0 fails to close the connection on bufio.Scanner errors while processing pre-receive hook input, allowing oversized input to bypass branch-protection checks.
Original NVD description (English source)
Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext. Attackers can supply arbitrary URLs through release asset download URLs, pull-request patch URLs, or OAuth avatar endpoints to reach internal services, cloud instance-metadata endpoints, or read local files such as the application configuration containing database credentials and signing secrets, with exfiltrated content persisted as migration release assets for later retrieval.