CVE-2026-68582
BOLA in Vikunja API allows unauthorized disclosure of kanban bucket metadata.
Is CVE-2026-68582 being exploited?
Not confirmed. CVE-2026-68582 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-68582?
CVE-2026-68582 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-68582?
Yes. A fix has been recorded for CVE-2026-68582. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68582 affect?
CVE-2026-68582 affects Vikunja >=0.24.0 and <=2.3.0, Self-hosted Vikunja multi-tenant instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68582?
Upgrade to Vikunja 2.4.0; revoke/rotate share links and audit access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Link-share holders or authenticated users can read other tenants' kanban bucket titles and creator user objects and enumerate project/view IDs.
Immediate action required
- affected>= 0.24.0 and < 2.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.