Security readout for executives and security teams
Plain-English summary
Vikunja versions before 2.1.0 may allow old password reset links to keep working forever. If someone obtained one reset token once, they could later reset that user’s password and take over the account. The vendor states version 2.1.0 patches the issue.
Executive priority
Treat as urgent for any organization using self-hosted Vikunja. The business impact is potential account takeover from a previously exposed reset link. Prioritize upgrade validation and token-exposure review, especially for administrative or high-value accounts.
Technical view
CVE-2026-28268 affects go-vikunja/vikunja before 2.1.0. The password reset mechanism failed to invalidate tokens after use, and token cleanup logic did not expire them correctly. The CVSS 3.1 score is 9.8, with network attack vector and no privileges or user interaction required once a token is obtained.
Likely exposure
Organizations running self-hosted Vikunja versions earlier than 2.1.0 are exposed. Risk is highest where reset tokens could be captured from logs, browser history, email compromise, or phishing. The provided sources do not identify hosted service exposure beyond the affected Vikunja product.
Exploitation context
The sources describe a serious account takeover condition but do not cite active exploitation, and the CVE is not marked KEV. Exploitation depends on obtaining a valid reset token; the vulnerability makes that token reusable indefinitely rather than one-time or time-limited.
Researcher notes
Public details identify the root cause as reusable password reset tokens plus defective cleanup logic. Avoid assuming exploitation in the wild without additional evidence. Validation should focus on version state, patch presence, and forensic review of reset-token exposure paths rather than active exploit reproduction.
Mitigation direction
- Upgrade Vikunja to version 2.1.0 or later.
- Review vendor advisory and changelog for deployment-specific upgrade guidance.
- Investigate possible exposure of password reset tokens in logs, emails, or browser artifacts.
- Monitor affected accounts for suspicious password resets or access changes.
Validation and detection
- Inventory all Vikunja deployments and record their versions.
- Confirm no deployment is running a version earlier than 2.1.0.
- Verify the applied build includes the referenced fixing commit.
- Review application logs for historical password reset activity and anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-459: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-640: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28268 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rfjg-6m84-crj2CVE reference · x_refsource_CONFIRM
- https://github.com/go-vikunja/vikunja/commit/5c2195f9fca9ad208477e865e6009c37889f87b2CVE reference · x_refsource_MISC
- https://vikunja.io/changelog/vikunja-v2.1.0-was-releasedCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incomplete Cleanup
Incomplete Cleanup represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Weak Password Recovery Mechanism for Forgotten Password
Weak Password Recovery Mechanism for Forgotten Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.