Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter
Only affects Vikunja 1.0.0 through 2.7.0 on the /api/v1 list endpoints, not /api/v2. The fix is in Vikunja 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Vikunja versions 1.0.0 through 2.7.0 (Go module code.vikunja.io/api) Only the /api/v1 list endpoints are affected; /api/v2 is not
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja from 1.0.0 before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to bypass service.maxitemsperpage by sending page=0 to /api/v1 list endpoints. Attackers can self-register and repeatedly request page=0 to force unbounded SQL queries, memory materialisation, and per-row query fan-out, degrading availability for other users.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects Vikunja versions 1.0.0 through 2.7.0 (Go module code.vikunja.io/api) Only the /api/v1 list endpoints are affected; /api/v2 is notUpgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
From 1.0.0 · fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123531
Is CVE-2026-123531 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can get past the maximum items-per-page limit using the page=0 parameter. This forces unbounded queries and full result sets, which can degrade availability for other users. The impact is availability only.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123531?
vikunja: from 1.0.0 before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions 1.0.0 through 2.7.0 (Go module code.vikunja.io/api) are affected, but only the /api/v1 list endpoints. The /api/v2 endpoints are not affected. To check a deployment, confirm the installed Vikunja version and whether it serves the /api/v1 list endpoints.Source: github.com, vulncheck.com
How do I fix CVE-2026-123531?
Upgrade Vikunja to version 2.7.1 or later.Source: github.com, vulncheck.com