Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values.
CVE-2026-25779
This medium-severity CVE scores 6.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EPSS
- 16.2%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
July 7, 2026
Advisory Details (5)
Auto-updated Jul 7, 2026Open Redirect via redirect_to in Gitea · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-j5r2-4c8j-xc3mv1.25.5
Patch available: go-gitea/gitea v1.25.5
https://github.com/go-gitea/gitea/releases/tag/v1.25.5Prevent redirect bypasses via backslash-encoded paths (#36660)
Fix merged in go-gitea/gitea PR #36716 on 2026-02-23 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36716Prevent redirect bypasses via backslash-encoded paths
Fix merged in go-gitea/gitea PR #36660 on 2026-02-22 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36660Vendor Advisories for CVE-2026-25779(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/go-gitea/gitea | — | 1.26.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 06:53 UTCEG score recompute▲ 6.10
- 2026-07-09 19:10 UTCEPSS rescore
Show 11 moreShow fewer
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 17:31 UTCMITRE cvelistV5CVSS v3 → 6.1 · severity → MEDIUM
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-03 22:27 UTCNVD update
- 2026-06-17 18:46 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-25779?
When was CVE-2026-25779 disclosed?
Is CVE-2026-25779 actively exploited?
What is the CVSS score of CVE-2026-25779?
How do I remediate CVE-2026-25779?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25779
Is Your Infrastructure Affected by CVE-2026-25779?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.