CVE-2026-52803gogs.io/gogs
NVD
Vulnerability Summary
Summary The Gogs application does NOT regenerate session IDs upon successful authentication. This allows an attacker to perform a session fixation attack where they can force a victim to use a known session ID, then hijack the session after the victim logs in. Vulnerable Code Snippet: ``` // File: internal/route/user/auth.go func SignInPost(c *context.Context, f form.SignIn) { // ... authentication logic ... // ADD THIS: Regenerate session ID on successful login c.Session.RegenerateID(c.Req.Context()) // ... set user session ... } ``` PoC - Attacker obtains the session ID by visiting login page β Session: i_like_gogs=c9af1981d493dc56 - Attacker forces the victim to use this session ID via: - Social engineering (send link with cookie) - XSS on subdomain - MITM attack - Physical access - Victim logs in using attacker's session ID β Session remains: c9af1981d493dc56 - Attacker uses the same session ID to access the victim's account β Complete account takeover achieved! Impact - Account Takeover: Complete compromise of user accounts - Data Breach: Access to private repositories and sensitive data - Privilege Escalation: If the admin account is compromised, full system access - Persistence: Attacker maintains access as long as the session is valid
Affected & Patched Versions
- gogs.io/gogs < 0.15.0
- gogs.io/gogs 0.15.0
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run gogs.io/gogs and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 16, 2026Published
- Nov 16, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new gogs.io/gogs CVEsYou are reading CVE-2026-52803. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore gogs.io/gogs CVEs
External References
Data last checked: Nov 22, 2026 17:00 UTC