Quick answers
- Is CVE-2026-123531 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123531 being exploited in the wild.
- How severe is CVE-2026-123531?
- High severity, with a CVSS score of 8.8, published 8 November 2026.
- Which products and versions are affected?
- Vikunja 1.0.0 before 2.7.1.
- Is there a fix for CVE-2026-123531?
- Yes: fixed in Vikunja 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123531 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-123531?
- 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: Vikunja 2.7.1
Technical details
The /api/v1 list endpoints validate the page query parameter only against negative values, allowing page=0 to bypass validation and be interpreted as "pagination not set", which results in a SQL query with no LIMIT clause. This causes the server to materialize the entire result set into memory and serialize it into a single response. Exploitation requires only the ability to register an account (enabled by default) and make HTTP requests to the API; no special privileges or authentication bypass is needed. The fix neutralizes the page=0 sentinel by converting it to page=1 in the handler layer.
Affected products
- Vikunja Vikunja 1.0.0 before 2.7.1
Timeline
- 2026-10-22: disclosed
- 2026-11-08: advisory