Vikunja 2.6.0 之前的版本存在一个资源耗尽漏洞,位于任务筛选端点中。该端点接受深度嵌套的筛选表达式,但未设置递归深度限制。经过身份验证的攻击者可以在筛选查询参数中提供数千个嵌套的括号,从而耗尽内存并导致 API 进程终止。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| go-vikunja | vikunja | 2.5.0 ~ 2.6.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-91972 | 7.5 HIGH | Vikunja before 2.6.0 Authentication Bypass via Unthrottled API |
| CVE-2026-91985 | 7.5 HIGH | Vikunja before 2.6.0 Privilege Escalation via Link Share Hash |
| CVE-2026-91973 | 7.5 HIGH | Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth |
| CVE-2026-91971 | 6.5 MEDIUM | Vikunja before 2.6.0 Denial of Service via Avatar Upload |
| CVE-2026-91979 | 6.5 MEDIUM | Vikunja before 2.6.0 Denial of Service via Decompression Bomb |
| CVE-2026-91970 | 6.5 MEDIUM | Vikunja before 2.6.0 Resource Exhaustion via Planka Migration |
| CVE-2026-91969 | 6.5 MEDIUM | vikunja before 2.6.0 Resource Exhaustion via CSV Migration |
| CVE-2026-91982 | 4.3 MEDIUM | Vikunja before 2.6.0 TOTP Secret Disclosure via API |
| CVE-2026-91980 | 4.3 MEDIUM | vikunja before 2.6.0 Team Enumeration via Project Share |
| CVE-2026-91981 | 4.3 MEDIUM | Vikunja before 2.6.0 User Enumeration via v2 API |
| CVE-2026-91983 | 4.3 MEDIUM | Vikunja before 2.6.0 API Token Scope Bypass via expand Parameter |
| CVE-2026-91984 | 4.3 MEDIUM | Vikunja before 2.6.0 Broken Object-Level Authorization via task-position |
No comments yet