Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, the application allows users to set weak passwords (e.g., 1234, password) without enforcing minimum strength requirements. Additionally, active sessions remain valid after a user changes their password. An attacker who compromises an account (via brute-force or credential stuffing) can maintain persistent access even after the victim resets their password. Version 2.0.0 contains a fix.
CVE-2026-27575
CRITICALPre-NVD 9.19.1—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-02-25. a secondary CVSS source baseline 9.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
February 25, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
Vikunja 2.0.0: Many security fixes and a few breaking changes
https://vikunja.io/changelog/vikunja-v2.0.0-was-releasedgithub Patch Available🟡 PoC Available
Weak Password Policy Combined with Persistent Sessions After Password Change · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-3ccg-x393-96v8Patch 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:04 UTCEG score recompute
- 2026-07-27 14:04 UTCGHSA enrichment
- 2026-07-27 13:57 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-27575?
CVE-2026-27575 is a critical vulnerability published on February 25, 2026. Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, the application allows users to set weak passwords (e.g., 1234, password) without enforcing minimum strength requirements. Additionally, active sessions remain valid after a user changes their password. An…
When was CVE-2026-27575 disclosed?
CVE-2026-27575 was first published in the National Vulnerability Database on February 25, 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-27575 actively exploited?
CVE-2026-27575 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.9% of all scored CVEs.
What is the CVSS score of CVE-2026-27575?
CVE-2026-27575 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-27575?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27575, 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-27575
Is Your Infrastructure Affected by CVE-2026-27575?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.