Answer in brief
CVE-2026-55065 records a High severity (CVSS 8.1) vulnerability in Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api. The current sources do not mark it as known exploited. The current feed maps go-vikunja/vikunja (generic), code.vikunja.io/api (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps go-vikunja/vikunja (generic), code.vikunja.io/api (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| go-vikunja/vikunjageneric | >= 0.24.6, < 2.4.0 | Not reported |
| code.vikunja.io/apigo | >=0.24.6,<2.4.0 | 2.4.0 |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.
Quoted source text, attributed separately from HOL analysis.