Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using conf.Auth.ActivateCodeLives (the account-activation lifetime), not conf.Auth.ResetPasswordCodeLives. The token lifetime is baked into the token itself at generation time and is re-extracted from the token at verification time, making RESET_PASSWORD_CODE_LIVES irrelevant to actual enforcement. When an administrator configures a shorter reset window (e.g., 10 minutes) for compliance or security reasons, reset tokens remain exploitable for the full activation lifetime instead, while the reset email falsely advertises the shorter expiry. This vulnerability is fixed in 0.14.3.
CVE-2026-52809
This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(medium)
- EPSS
- 10.2%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 24, 2026Password-reset tokens use account-activation lifetime, ignoring RESET_PASSWORD_CODE_LIVES · Advisory · gogs/gogs · GitHub
https://github.com/gogs/gogs/security/advisories/GHSA-5c3f-6486-3g7g0.14.3
Patch available: gogs/gogs v0.14.3
https://github.com/gogs/gogs/releases/tag/v0.14.3Vendor Advisories for CVE-2026-52809(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 03:33 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:50 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:06 UTCEG score recompute
- 2026-07-03 01:15 UTCEG score recompute
- 2026-07-02 00:30 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:46 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 22:58 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 22:14 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 21:30 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 20:46 UTCEG score recompute
- 2026-06-25 20:03 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
Show 2 moreShow fewer
- 2026-06-24 19:19 UTCEG score recompute
- 2026-06-23 17:22 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-52809?
When was CVE-2026-52809 disclosed?
Is CVE-2026-52809 actively exploited?
What is the CVSS score of CVE-2026-52809?
How do I remediate CVE-2026-52809?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52809
Is Your Infrastructure Affected by CVE-2026-52809?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.