Medium severity · published Oct 17, 2026
CVE-2026-111920
Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions
4.3
CVSS
0.2%
EPSS
No
On KEV
Description
Vikunja 2.6.0 contains a broken access control flaw in getProjectAccessForUser (pkg/models/project_access.go), which resolves a user's effective project permission as the maximum over the project tree, silently overriding explicit lower-permission shares on sub-projects. A collaborator with write access on a parent project but read-only access to a child project can modify the child project's tasks and content.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 9% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
VI
vikunja · go-vikunja
2.6.0 · source: vendor
Affected product
VI
vikunja
go-vikunja
More from vikunja
9.8
CVE-2026-28268
Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
9.6
CVE-2026-33334
Vikunja Desktop: Any frontend XSS escalates to Remote Code Execution due to nodeIntegration
9.1
CVE-2026-34727
Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
9.1
CVE-2026-27575
Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change
8.8
CVE-2026-33336
Vikunja Desktop vulnerable to Remote Code Execution via same-window navigation