# CVE-2026-62376: Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access

> Attackers with database read access can steal plaintext password-reset tokens to take over user accounts in Vikunja.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-r6w9-259g-gwrv, GO-2026-6748

## What is CVE-2026-62376?

CVE-2026-62376 is a high-severity vulnerability in go-vikunja vikunja, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vikunja is an open-source self-hosted task management platform. Versions prior to 2.4.0 store password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` 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. Version 2.4.0 fixes the issue.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-62376?

3 open source packages ship an affected version, including code.vikunja.io/api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | All versions | None |
| `code.vikunja.io/api` | Go | All versions | 2.4.0 |
| `code.vikunja.io/api` | Go | All versions | 2.4.0 |

## How do I fix CVE-2026-62376?

Upgrade code.vikunja.io/api to 2.4.0 or later.

## Is CVE-2026-62376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62376 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62376 and fix it if it is affected.

What it is: CVE-2026-62376 is a high-severity vulnerability in go-vikunja vikunja, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62376 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected all versions; no fix listed
- code.vikunja.io/api (Go): affected all versions; fixed in 2.4.0
- code.vikunja.io/api (Go): affected all versions; fixed in 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62376/ (Markdown: https://insights.sbomify.com/CVE-2026-62376/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62376
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62376
- OSV: https://osv.dev/vulnerability/CVE-2026-62376

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62376/
Summaries are generated and may contain mistakes; the official description above is the record.