CVE-2026-68582: Authorization Bypass Through User-Controlled Key in go-vikunja vikunja
Vikunja versions from 0.24.0 up to and including 2.3.0 have a broken object level authorization vulnerability in the task-collection endpoint. This flaw allows holders of any project share link to read kanban bucket titles and user information from other tenants' project views without proper authorization. The vulnerability does not disclose task contents beyond the share's own project. It also enables an existence oracle for project/view IDs. The issue is fixed starting from version 2.4.0.
AI Analysis
Technical Summary
CVE-2026-68582 is a broken object level authorization (BOLA) vulnerability in the go-vikunja vikunja product affecting versions >=0.24.0 and <=2.3.0. The vulnerability exists in the GET /api/v1/projects/{project}/views/{view}/tasks endpoint, where the requested project view is loaded from the URL path without verifying the caller's authorization. While the task scope is limited to the share's project for link-share token holders, the view parameter is attacker-controlled and not re-validated, allowing unauthorized reading of kanban bucket titles and full created_by user objects (username, name, id) across tenants. Additionally, the missing authorization check creates a project/view-ID existence oracle via differing HTTP 404 responses. Task contents themselves remain protected and are not disclosed. The vulnerability is fixed in version 2.4.0.
Potential Impact
An attacker with any project share link can access sensitive metadata from other tenants' project views, including kanban bucket titles and user identity information, violating tenant data isolation. This could lead to information disclosure and privacy violations. The vulnerability also allows attackers to confirm the existence of project/view IDs, potentially aiding further reconnaissance. However, actual task content data remains protected and is not exposed.
Mitigation Recommendations
A fix for this vulnerability is available in vikunja version 2.4.0. Users should upgrade to version 2.4.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fixed version, so users should consult the vendor advisory for the latest remediation guidance.
CVE-2026-68582: Authorization Bypass Through User-Controlled Key in go-vikunja vikunja
Description
Vikunja versions from 0.24.0 up to and including 2.3.0 have a broken object level authorization vulnerability in the task-collection endpoint. This flaw allows holders of any project share link to read kanban bucket titles and user information from other tenants' project views without proper authorization. The vulnerability does not disclose task contents beyond the share's own project. It also enables an existence oracle for project/view IDs. The issue is fixed starting from version 2.4.0.
CVSS v4.0
Score 9.3critical
Affected software
pkg:golang/github.com/go-vikunja/vikunjaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-68582 is a broken object level authorization (BOLA) vulnerability in the go-vikunja vikunja product affecting versions >=0.24.0 and <=2.3.0. The vulnerability exists in the GET /api/v1/projects/{project}/views/{view}/tasks endpoint, where the requested project view is loaded from the URL path without verifying the caller's authorization. While the task scope is limited to the share's project for link-share token holders, the view parameter is attacker-controlled and not re-validated, allowing unauthorized reading of kanban bucket titles and full created_by user objects (username, name, id) across tenants. Additionally, the missing authorization check creates a project/view-ID existence oracle via differing HTTP 404 responses. Task contents themselves remain protected and are not disclosed. The vulnerability is fixed in version 2.4.0.
Potential Impact
An attacker with any project share link can access sensitive metadata from other tenants' project views, including kanban bucket titles and user identity information, violating tenant data isolation. This could lead to information disclosure and privacy violations. The vulnerability also allows attackers to confirm the existence of project/view IDs, potentially aiding further reconnaissance. However, actual task content data remains protected and is not exposed.
Mitigation Recommendations
A fix for this vulnerability is available in vikunja version 2.4.0. Users should upgrade to version 2.4.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fixed version, so users should consult the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-31T11:56:29.760Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6f3c9fbf32cb7a348adf7b
Added to database: 08/02/2026, 12:48:31 UTC
Last enriched: 08/02/2026, 13:02:55 UTC
Last updated: 08/02/2026, 13:38:30 UTC
Views: 44
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.