Quick answers
- Is CVE-2026-123524 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123524 being exploited in the wild.
- How severe is CVE-2026-123524?
- Medium severity, with a CVSS score of 5.7, published 8 November 2026.
- Which products and versions are affected?
- Vikunja 0.23.0 to 2.7.0.
- Is there a fix for CVE-2026-123524?
- Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123524 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-123524?
- 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
Technical details
The vulnerability is an authorization bypass in webhook payload construction. Webhook event handlers reload task data using the triggering user's permissions rather than the webhook creator's permissions. Related tasks are included in the payload with full details but are filtered only by the doer's access level, not the webhook recipient's. An attacker with write access to one shared project can leak titles, descriptions, dates, priorities, and other task metadata from private projects every time an authorized user modifies a linked task.
Affected products
- Vikunja Vikunja 0.23.0 to 2.7.0
Timeline
- 2026-10-22: advisory
- 2026-11-08: disclosed