{"id":"CVE-2026-123531","published":"2026-11-08T02:16:43.190","lastModified":"2026-11-08T02:16:43.317","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.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cwes":["CWE-400"],"vendors":[],"products":[],"references":[{"url":"https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28","tags":[]},{"url":"https://www.vulncheck.com/advisories/vikunja-1.0.0-before-2.7.1-pagination-limit-bypass-via-page-0-parameter","tags":[]}],"exploitRefs":[{"url":"https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v579-5fwc-gr28","tags":[]}],"hasPoc":true,"ai":{"summary":"Authenticated users in Vikunja versions before 2.7.1 can bypass the service.maxitemsperpage limit by sending page=0 to /api/v1 list endpoints, triggering uncontrolled SQL query execution and memory consumption. This allows resource exhaustion via repeated requests, degrading service availability for other users.","exploitability":"Authenticated attackers with self-registration capability can exploit this trivially by issuing repeated HTTP requests with page=0 to paginated list endpoints.","blast_radius":"Successful exploitation can cause significant performance degradation or denial of service across the entire Vikunja instance, affecting all users and potentially cascading to dependent services.","remediation":"Upgrade to Vikunja 2.7.1 or later, which fixes the uncontrolled resource consumption vulnerability by properly handling page=0 requests.","detection":"Defenders should monitor for repeated HTTP 200 responses from /api/v1/* endpoints with unusually high response sizes or durations, especially when accompanied by page=0 query parameters in logs; elevated database CPU/memory usage correlated with authenticated user sessions may also indicate exploitation.","tags":["dos","resource-exhaustion","auth-bypass","web","sql-injection"],"model":"garnet-coder","analyzedAt":"2026-11-08T09:53:50.741Z"}}