Vikunja is an open-source self-hosted task management platform. Prior to 2.4.0, POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}/tasks accepts a body supplied task_id but TaskBucket.CanUpdate in pkg/models/kanban_task_bucket.go authorizes only the project, view, and bucket from the URL. updateTaskBucket then calls Task.ReadOne without a separate task permission check, returns the victim task contents, and can update the task done state when the attacker chooses a done bucket. Because task identifiers are global sequential values, an authenticated user can enumerate cross-tenant tasks and modify their completion metadata through both the v1 and v2 routes that share this model. This issue is fixed in version 2.4.0.
CVE-2026-55066
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
September 9, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026Cross-tenant IDOR in kanban move-task endpoint via unauthorized body task_id · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-5pg6-m483-7vrgv2.4.0
Patch available: go-vikunja/vikunja v2.4.0
https://github.com/go-vikunja/vikunja/releases/tag/v2.4.0Fix security vulnerabilities
Fix merged in go-vikunja/vikunja PR #3239 on 2026-07-19 — awaiting tagged release
https://github.com/go-vikunja/vikunja/pull/3239commit 36cdc2ce2be0 (go-vikunja/vikunja)
Fix landed in go-vikunja/vikunja commit 36cdc2ce2be0 — awaiting tagged release
https://github.com/go-vikunja/vikunja/commit/36cdc2ce2be0b8ccc74227d178b92047d59cd65fVendor Advisories for CVE-2026-55066(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.vikunja.io/api | — | 2.4.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 44× 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-09-20 21:55 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:59 UTCEG score recompute
- 2026-09-18 21:28 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:25 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 21:29 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:11 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 08:48 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 20:55 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 20:59 UTCEG score recompute
- 2026-09-11 21:03 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 21:07 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 00:27 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 20:24 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 20:24 UTCEG score recompute
Show 19 moreShow fewer
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 20:27 UTCEG score recompute
- 2026-09-04 20:32 UTCEG score recompute
- 2026-09-04 08:21 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 20:24 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 19:37 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 07:30 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 19:31 UTCEG score recompute
- 2026-08-31 19:07 UTCEG score recompute
- 2026-08-30 20:18 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:20 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 17:11 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-55066?
When was CVE-2026-55066 disclosed?
Is CVE-2026-55066 actively exploited?
What is the CVSS score of CVE-2026-55066?
How do I remediate CVE-2026-55066?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55066
Is Your Infrastructure Affected by CVE-2026-55066?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.