dbcve.org
CWE-324Weakness · CWE-324

CVE-2026-52809

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Gogs prior to 0.14.3, password-reset tokens are generated using the account-activation lifetime (ActivateCodeLives) instead of the intended password-reset lifetime (ResetPasswordCodeLives). The token lifetime is embedded in the token at generation and extracted at verification, bypassing the ResetPasswordCodeLives configuration entirely, causing tokens to remain valid far longer than administrators expect.

MitigationUpgrade Gogs to version 0.14.3 or later to ensure password-reset tokens use the correct configuration value and respect the intended expiry window.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Gogs version
    Access the Gogs admin panel (typically at /admin) or check the binary/version file shipped with your installation
    Affected if The installed version is prior to 0.14.3 (e.g., 0.14.2, 0.14.1, 0.14.0, or earlier)
  2. Locate configuration file
    Find the Gogs configuration file (custom/conf/app.ini or similar) - the location depends on your installation method
    Affected if Configuration file exists and Gogs version is affected (prior to 0.14.3)
  3. Compare token lifetime settings
    Inspect the [security] section in the config for ActivateCodeLives and ResetPasswordCodeLives values - note that the bug causes ActivateCodeLives to be used for password resets regardless of ResetPasswordCodeLives setting
    Affected if Both settings exist and ActivateCodeLives differs from ResetPasswordCodeLives, with the installed version being vulnerable
  4. Check if password reset is enabled
    Verify that the password reset feature is enabled in Gogs settings - look for ENABLE_PASSWORD_RESET or similar configuration flag
    Affected if Password reset is enabled and Gogs version is prior to 0.14.3 - this means tokens may live longer than intended

You are affected if your Gogs version is prior to 0.14.3 AND password reset is enabled, regardless of your ResetPasswordCodeLives configuration value.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gogs to version 0.14.3 or later to ensure password-reset tokens use the correct configuration value and respect the intended expiry window.

Recommended fix High confidence

Gogs version 0.14.3

  1. 1. Back up your Gogs database and configuration files (app.ini, custom directory) before upgrading.
  2. 2. Download Gogs version 0.14.3 from the official GitHub releases page (github.com/gogs/gogs/releases).
  3. 3. Stop the Gogs service.
  4. 4. Replace the existing Gogs binary with the new version 0.14.3 binary.
  5. 5. Ensure the configuration option 'RESET_PASSWORD_CODE_LIVES' in app.ini is set to your desired token lifetime (e.g., 10 minutes).
  6. 6. Start the Gogs service.
  7. 7. Verify that password-reset tokens now expire according to the RESET_PASSWORD_CODE_LIVES setting rather than the ActivateCodeLives setting.
Caveat Review release notes for 0.14.3 to check for any breaking changes between your current version and 0.14.3; major version jumps may introduce behavioral changes.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52809 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data