Medium 4.3Published Oct 17, 2026

CVE-2026-111920Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions

Updated under an hour ago (Oct 27, 2026, 4:10 PM ET)

Does this affect you?

It affects go-vikunja vikunja. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for go-vikunja vikunja

Exploited in the last 30 days

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.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness (CWE): CWE-269
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Deferred
Record last updated: Oct 18, 2026
First seen by InfoSec Signals: Oct 17, 2026

Affected products

Affected products

go-vikunja vikunja go_vikunja:vikunja (from the name)	2.6.0	CNA record

References

References

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

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.