# CVE-2026-28268: Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse

> Attackers can achieve persistent account takeover by reusing intercepted password reset tokens due to a failure to invalidate them after use.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 27 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-rfjg-6m84-crj2, GO-2026-4575

## What is CVE-2026-28268?

CVE-2026-28268 is a critical vulnerability in go-vikunja vikunja, published on 27 Feb 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.1.0 have a business logic vulnerability exists in the password reset mechanism of vikunja/api that allows password reset tokens to be reused indefinitely. Due to a failure to invalidate tokens upon use and a critical logic bug in the token cleanup cron job, reset tokens remain valid forever. This allows an attacker who intercepts a single reset token (via logs, browser history, or phishing) to perform a complete, persistent account takeover at any point in the future, bypassing standard authentication controls. Version 2.1.0 contains a patch for the issue.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-459 (Incomplete Cleanup)

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

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


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

Products: Vikunja Vikunja.

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

Upgrade to a fixed version.

## Is CVE-2026-28268 being exploited?

There is no known exploitation of CVE-2026-28268 in the wild and no public exploit code.

## Other vulnerabilities in go-vikunja vikunja

- [CVE-2026-27575](https://insights.sbomify.com/CVE-2026-27575/): Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change (critical 9.1)
- [CVE-2026-25935](https://insights.sbomify.com/CVE-2026-25935/): Vikunja Affected by XSS Via Task Preview (high 8.6)
- [CVE-2026-35595](https://insights.sbomify.com/CVE-2026-35595/): Vikunja Affected by Privilege Escalation via Project Reparenting (high 8.3)
- [CVE-2026-33316](https://insights.sbomify.com/CVE-2026-33316/): Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement (high 8.1)
- [CVE-2026-33678](https://insights.sbomify.com/CVE-2026-33678/): Vikunja has IDOR in Task Attachment ReadOne Allows Cross-Project File Access and Deletion (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28268 is a critical vulnerability in go-vikunja vikunja, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28268 in the wild and no public exploit code.

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

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-28268/ (Markdown: https://insights.sbomify.com/CVE-2026-28268/index.md)
```

## Sources

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

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