Quick answers
- Is CVE-2026-123509 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123509 being exploited in the wild.
- How severe is CVE-2026-123509?
- Medium severity, with a CVSS score of 4.3, published 8 November 2026.
- Which products and versions are affected?
- Vikunja before 2.7.1.
- Is there a fix for CVE-2026-123509?
- Yes: fixed in 2.7.1. Until then: Limit the number of kanban buckets per view to approximately 50 at write time in validateProjectViewFilters and enforce a per-view manual-bucket cap in the Bucket.Create function. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123509 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-123509?
- Check whether you run Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.7.1
Limit the number of kanban buckets per view to approximately 50 at write time in validateProjectViewFilters and enforce a per-view manual-bucket cap in the Bucket.Create function.
Technical details
An uncontrolled resource consumption vulnerability in the kanban bucket creation allows users with project write or view admin permissions to create arbitrary buckets without any count limit. When reading kanban views, the API loops over all buckets and executes a SELECT and COUNT query per bucket, creating query fan-out proportional to the number of buckets created. The vulnerability is in ProjectView.BucketConfiguration having no length cap and Bucket.Create lacking per-view count restrictions.
Affected products
- Vikunja Vikunja before 2.7.1
Timeline
- 2026-10-22: disclosed
- 2026-11-08: advisory