Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.
CVE-2026-33473
MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence
Score 5.7 from GitHub Security Advisory published 2026-03-20. a secondary CVSS source baseline 5.7; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 5.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.7
- EG Score
- 5.7(medium)
- EG Risk
- 30(Track)EG Risk 30/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 computedSeverity57% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/go-vikunja/vikunja/security/advisories/GHSA-p747-qc5p-773r
- security-advisories@githubhttps://vikunja.io/changelog/vikunja-v2.2.0-was-released
- security-advisories@githubhttps://vikunja.io/changelog/vikunja-v2.2.2-was-released
Patch 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(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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:29 UTCEG score recompute
- 2026-07-27 14:29 UTCGHSA enrichment
Related CVEs(same product + same CWE)
Same product
9 showngo:code.vikunja.io/api
Same CWE
10 shownCWE-287
Frequently asked(4)
What is CVE-2026-33473?
CVE-2026-33473 is a medium vulnerability published on March 24, 2026. Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.
When was CVE-2026-33473 disclosed?
CVE-2026-33473 was first published in the National Vulnerability Database on March 24, 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.
What is the CVSS score of CVE-2026-33473?
CVE-2026-33473 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-33473?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33473, 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-33473
Is Your Infrastructure Affected by CVE-2026-33473?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.