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.
CVE-2026-28268
CRITICALPre-NVD 9.89.8—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-02-28. a secondary CVSS source baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
February 27, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026Patch available. Sources: github_commit, github.
generic
Vikunja 2.1.0: One security fix and some improvements
https://vikunja.io/changelog/vikunja-v2.1.0-was-releasedgithub Patch Available
Account Takeover via Password Reset Token Reuse · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rfjg-6m84-crj2github_commit
commit 5c2195f9fca9 (go-vikunja/vikunja)
Fix landed in go-vikunja/vikunja commit 5c2195f9fca9 — awaiting tagged release
https://github.com/go-vikunja/vikunja/commit/5c2195f9fca9ad208477e865e6009c37889f87b2Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| go | code.vikunja.io/api | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:03 UTCEG score recompute
- 2026-07-27 14:03 UTCGHSA enrichment
- 2026-07-27 13:55 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-28268?
CVE-2026-28268 is a critical vulnerability published on February 27, 2026. 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…
When was CVE-2026-28268 disclosed?
CVE-2026-28268 was first published in the National Vulnerability Database on February 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28268 actively exploited?
CVE-2026-28268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.6% of all scored CVEs.
What is the CVSS score of CVE-2026-28268?
CVE-2026-28268 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-28268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28268, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-28268
Is Your Infrastructure Affected by CVE-2026-28268?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.