Gogs has an Open Redirect via redirect_to

Exploitation

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

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-52802: 0.55% estimated exploitation activity in the next 30 days; percentile 46.32 (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.

Summary An open redirect vulnerability exists in Gogs where attacker-controlled redirectto parameters can bypass validation, allowing redirection to arbitrary external sites. Details All redirects in Gogs that are validated via the IsSameSite function are vulnerable: The function only inspects the first two characters of the URL string. This check fails to account for directory traversal sequences followed by backslashes. For example: The IsSameSite function checks the input supplied to the redirectto query parameter value /a/../\example.com and considers it valid. Because web browsers normalize backslashes \ to forward slashes /, the normalized URL becomes //example.com. The normalized URL becomes: Resulting in a cross-origin redirect. This affects all endpoints using the redirectto query parameter, including login and other post-action flows. PoC 1. An attacker can provide a user with a link to login to Gogs with a redirectto query parameter that redirects a user to a site the…

Published by the source

23 Jun 2026, 16:42 UTC

Last modified by the source

21 Jul 2026, 13:36 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xxhq-69mf-w8cr

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

# Patch Next advisory brief: CVE-2026-52802

Advisory: Gogs has an Open Redirect via redirect_to
IDs: CVE-2026-52802, GHSA-xxhq-69mf-w8cr
Record: https://patchnext.com/advisories/cve-2026-52802 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gogs.io/gogs 0.14.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go gogs.io/gogs: affected <= 0.14.2; fixed in 0.14.3

## Suggested inspection (read-only)
- Go gogs.io/gogs: 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 gogs.io/gogs.
- 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-xxhq-69mf-w8cr (GitHub-reviewed advisory GHSA-xxhq-69mf-w8cr lists affected ranges: Go gogs.io/gogs >=0 <=0.14.2)

Commands are suggestions: review each one before running it.