CVE-2026-111920

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 4.0

5.3CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

0.2% chance of exploitation in the next 30 days; higher than 8% of CVEs (scores of 2026-10-25)

CWE

CWE-269

Published

2026-10-17

Modified

2026-10-19

Record from

the NVD, synced 2026-10-21

Packages (OSV)

References

• https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pjr3-86v4-5p7w
• https://www.vulncheck.com/advisories/vikunja-2.6.0-broken-access-control-via-inherited-project-permissions
• https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pjr3-86v4-5p7w

Check your stackJSON