Quick answers
- Is CVE-2026-123527 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123527 being exploited in the wild.
- How severe is CVE-2026-123527?
- Medium severity, with a CVSS score of 5.4, published 8 November 2026.
- Which products and versions are affected?
- Vikunja 2.4.0 before 2.7.1.
- Is there a fix for CVE-2026-123527?
- 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-123527 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-123527?
- 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 stems from separate permission key generation for v1 and v2 API routes that collide on the same keys but have opposite HTTP method assignments (e.g., v1 "background" = GET, v2 "background" = DELETE). The tokenAuthorizesRoute function accepts matches in either route table without accounting for method differences, allowing a token scoped for one verb to authorize a different verb on the alternate API version. This requires an attacker to possess a valid API token with project access and make requests to the opposing API version.
Affected products
- Vikunja Vikunja 2.4.0 before 2.7.1
Timeline
- 2026-10-22: disclosed: GitHub Security Advisory published
- 2026-11-08: advisory: NVD and public advisory release