Open Redirect in github.com/go-gitea/gitea (CVE-2026-25779)
Summary
Vulnerability in github.com/go-gitea/gitea (CVE-2026-25779). Risk of unauthorized operations or information disclosure. Exploitable via Referer header. Mitigation: upgrade to 1.26.0 or later.
Original description
The description as published by the source.
Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-25779 has been found in github.com/go-gitea/gitea.
Attackers can target a specific entry point like Referer header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade github.com/go-gitea/gitea to 1.26.0 or later.
If unsure, ask your IT team or search "github.com/go-gitea/gitea CVE-2026-25779" on the vendor's site.
CVE-2026-25779 (github.com/go-gitea/gitea) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Referer header / urlIsRelative / example.com
Patched: 1.26.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in github.com/go-gitea/gitea. Attackers reach the vulnerable code path via Referer header without authentication.
Check the vendor advisory for the affected versions of github.com/go-gitea/gitea. Attack surface: Referer header / urlIsRelative / example.com.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.26.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/go-gitea/gitea' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/go-gitea/gitea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/go-gitea/giteaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/go-gitea/gitea to 1.26.0ステージング環境で 1.26.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory blog.gitea.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com