Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CVE-2026-35595— Vikunja Affected by Privilege Escalation via Project Reparenting

CVSS 8.3 · High EPSS 0.03% · P11
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-35595

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

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.

Vulnerability Title
Vikunja Affected by Privilege Escalation via Project Reparenting
Source: NVD (National Vulnerability Database)
Vulnerability Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the CanUpdate check at pkg/models/project_permissions.go:139-148 only requires CanWrite on the new parent project when changing parent_project_id. However, Vikunja's permission model uses a recursive CTE that walks up the project hierarchy to compute permissions. Moving a project under a different parent changes the permission inheritance chain. When a user has inherited Write access (from a parent project share) and reparents the child project under their own project tree, the CTE resolves their ownership of the new parent as Admin (permission level 2) on the moved project. This vulnerability is fixed in 2.3.0.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Source: NVD (National Vulnerability Database)
Vulnerability Type
特权管理不恰当
Source: NVD (National Vulnerability Database)
Vulnerability Title
Vikunja 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Vikunja是Vikunja开源的一个待办事项应用程序。 Vikunja 2.3.0之前版本存在安全漏洞，该漏洞源于更改父项目ID时的权限检查逻辑与递归权限继承模型不一致，可能导致用户通过移动项目获得管理员权限。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
go-vikunjavikunja < 2.3.0 -

II. Public POCs for CVE-2026-35595

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium
Qwen3.6-35B-A3B · 10625 chars
Paid plan includes:
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2026-35595

请登录查看更多情报信息。

Same Patch Batch · go-vikunja · 2026-04-10 · 11 CVEs total

CVE-2026-347277.4 HIGHVikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
CVE-2026-355946.5 MEDIUMVikunja Link Share JWT tokens remain valid for 72 hours after share deletion or permission
CVE-2026-355996.5 MEDIUMVikunja has an Algorithmic Complexity DoS in Repeating Task Handler
CVE-2026-355975.9 MEDIUMVikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout
CVE-2026-356005.4 MEDIUMVikunja has HTML Injection via Task Titles in Overdue Email Notifications
CVE-2026-356025.4 MEDIUMVikunja has a File Size Limit Bypass via Vikunja Import
CVE-2026-355964.3 MEDIUMVikunja has Broken Access Control on Label Read via SQL Operator Precedence Bug
CVE-2026-355984.3 MEDIUMVikunja has Missing Authorization on CalDAV Task Read
CVE-2026-401034.3 MEDIUMVikunja's Scoped API tokens with projects.background permission can delete project backgro
CVE-2026-356014.1 MEDIUMVikunja has an iCalendar Property Injection via CRLF in CalDAV Task Output

IV. Related Vulnerabilities

Same product: vikunja
Same vendor: go-vikunja
Same weakness: CWE-269

V. Comments for CVE-2026-35595

No comments yet

Leave a comment