Gitea: Open Redirect via redirect_to

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-25779: 0.30% estimated exploitation activity in the next 30 days; percentile 23.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Details Despite the validation within urlIsRelative in modules/httplib/url.go, an open redirect is still possible due to usage of directory traversal sequences plus a back-slash in the "redirectto" parameter. PoC When a user uses this URL to login: https://gitea.com/user/login?redirectto=/a/../\example.com They would be redirected to example.com upon a successful login to their gitea account. Impact Phishing: Attackers can use trusted domain links to redirect victims to credential-harvesting pages OAuth/SSO Token Theft: In authentication flows, authorization codes or tokens may leak via redirect Referer Leakage: Sensitive URL parameters may be exposed to attacker domains via the Referer header Cache Poisoning: In deployments with shared caches, malicious redirects may be cached and served to other users

Published by the source

17 Jun 2026, 18:10 UTC

Last modified by the source

17 Jun 2026, 18:10 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j5r2-4c8j-xc3m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25779

Advisory: Gitea: Open Redirect via redirect_to
IDs: CVE-2026-25779, GHSA-j5r2-4c8j-xc3m
Record: https://patchnext.com/advisories/cve-2026-25779 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-gitea/gitea 1.26.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-gitea/gitea: affected <= 1.25.4; fixed in 1.26.0

## Suggested inspection (read-only)
- Go github.com/go-gitea/gitea: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-gitea/gitea.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j5r2-4c8j-xc3m (GitHub-reviewed advisory GHSA-j5r2-4c8j-xc3m lists affected ranges: Go github.com/go-gitea/gitea >=0 <=1.25.4)

Commands are suggestions: review each one before running it.