Quick answers
- Is CVE-2026-82402 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82402 being exploited in the wild.
- How severe is CVE-2026-82402?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Gogs prior to 0.15.0+dev.
- Is there a fix for CVE-2026-82402?
- Yes: fixed in 0.15.0+dev. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82402 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82402?
- Check whether you run Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.15.0+dev
Technical details
The vulnerability stems from a normalization mismatch in URL validation: the IsSameSite function validates a normalized form of redirect targets, but the getRedirect function and other callers use the original, non-normalized value in the HTTP Location response header. Specifically, backslash characters are handled differently during validation versus when constructing the redirect, allowing an unauthenticated attacker to bypass same-site checks via the /redirect endpoint and similar post-action redirect flows. The attack is network-accessible and requires no authentication or user interaction beyond clicking a malicious link.
Affected products
- Gogs Gogs prior to 0.15.0+dev
Timeline
- 2026-10-14: disclosed