Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access
CVE-2026-62376GHSA-r6w9-259g-gwrv
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (code.vikunja.io/api 2.4.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- <= 2.3.0
- Fixed in
- 2.4.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6748 lists affected ranges: Go code.vikunja.io/api >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-r6w9-259g-gwrv lists affected ranges: Go code.vikunja.io/api >=0 <2.4.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r6w9-259g-gwrv lists affected ranges: Go code.vikunja.io/api >=0 <=2.3.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-62376: 0.28% estimated exploitation activity in the next 30 days; percentile 20.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Vikunja stores password-reset, email-confirmation, and account-deletion tokens in the usertokens table in plaintext. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords. Details pkg/user/token.go — genToken() stores the raw random string directly: Lookup also uses plaintext equality: Affected token types: - TokenPasswordReset (pkg/user/userpasswordreset.go:120) - TokenEmailConfirm (pkg/user/usercreate.go:101, pkg/user/updateemail.go:88) - TokenAccountDeletion (pkg/user/delete.go:102) Note: CalDAV tokens correctly use generateHashedToken with bcrypt — the same protection is absent for the above types. PoC Impact Any read access to the database (leaked backup, cloud misconfiguration, secondary SQLi) allows an attacker to take over every user account with a pending reset token within the 24-hour token lifetime. Full…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-r6w9-259g-gwrv
- Revision 2 · amended ·
Amended from osv record GO-2026-6748
- Revision 1 · created ·
Published from osv record GHSA-r6w9-259g-gwrv
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-62376 Advisory: Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access IDs: CVE-2026-62376, GHSA-r6w9-259g-gwrv Record: https://patchnext.com/advisories/cve-2026-62376 (revision 3, source checked 26 Oct 2026, 15:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: code.vikunja.io/api 2.4.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go code.vikunja.io/api: affected <= 2.3.0; fixed in 2.4.0 ## Suggested inspection (read-only) - Go code.vikunja.io/api: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on code.vikunja.io/api. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6748 (OSV record GO-2026-6748 lists affected ranges: Go code.vikunja.io/api >=0) - Verified: https://osv.dev/vulnerability/GHSA-r6w9-259g-gwrv (OSV record GHSA-r6w9-259g-gwrv lists affected ranges: Go code.vikunja.io/api >=0 <2.4.0 (fixed)) - Verified: https://github.com/advisories/GHSA-r6w9-259g-gwrv (GitHub-reviewed advisory GHSA-r6w9-259g-gwrv lists affected ranges: Go code.vikunja.io/api >=0 <=2.3.0) Commands are suggestions: review each one before running it.
Loading voting…