Quick answers
- Is CVE-2026-52809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52809 being exploited in the wild.
- How severe is CVE-2026-52809?
- Medium severity, with a CVSS score of 6.8, published 24 June 2026.
- Which products and versions are affected?
- gogs.io/gogs (Go) < 0.14.3, SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.14.3; Gogs < 0.14.3.
- Is there a fix for CVE-2026-52809?
- Yes. gogs.io/gogs (Go): upgrade to 0.14.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52809 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52809?
- Check whether you run gogs.io/gogs (Go) or 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
- gogs.io/gogs (Go): upgrade to 0.14.3 or later
go get gogs.io/gogs@v0.14.3
Technical details
In Gogs versions prior to 0.14.3, password-reset tokens are generated using the 'ActivateCodeLives' configuration value instead of 'ResetPasswordCodeLives'. The vulnerability stems from the fact that the token's lifetime is hardcoded into the token string itself at generation time and re-extracted during verification, rendering the specific password-reset expiration setting irrelevant. While the reset email may falsely claim a short expiry (e.g., 10 minutes), the token remains cryptographically valid for the duration of the account activation window (often hours or days). An attacker who obtains a reset token can perform an account takeover even after the intended expiration window has passed. This issue is fixed in version 0.14.3.
Affected products
- Gogs Gogs < 0.14.3
Identifiers
- CVE-2026-52809
- GHSA-5c3f-6486-3g7g
- GO-2026-5140
Timeline
- 2026-06-07: patched: Version 0.14.3 released
- 2026-06-19: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD