CVE-2026-52809 json
Gogs: Password-reset tokens use account-activation lifetime, ignoring RESET_PASSWORD_CODE_LIVES
published 4mo ago modified 8d ago also EUVD-2026-39079 , GHSA-5c3f-6486-3g7g , GO-2026-5140
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go gogs.io/gogs 0.14.3
- gogs gogs 0.14.3
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/gogs/gogs@187e9c5 commit
- github.com/gogs/gogs#8328 pull request
- github.com/gogs/gogs/releases/tag/v0.14.3 release
Is CVE-2026-52809 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/gogs/gogs/security/advisories/GHSA-5c3f-6486-3g7g referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | gogs.io/gogs | <0.14.3 all versions |
0.14.3 |
Affected products
- gogs gogs
Classification
References
-
github.com
/gogs/gogs/pull/8328
web
-
github.com
/gogs/gogs/commit/187e9c557930eb4a8b9b1502ee45cccf3255ee7f
web
-
github.com
/gogs/gogs/security/advisories/GHSA-5c3f-6486-3g7g
exploit, web, advisory
-
github.com
/gogs/gogs/releases/tag/v0.14.3
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-52809
advisory
-
github.com
/gogs/gogs
package
Sources
- CVE List CVE-2026-52809
- GitHub Advisory GHSA-5c3f-6486-3g7g
- NVD CVE-2026-52809
- OSV GO-2026-5140
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.