CVE-2026-111920 json
Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions
published last mo. modified 12d ago also EUVD-2026-103288 , GHSA-pjr3-86v4-5p7w , GO-2026-6745
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-111920 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 22d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pjr3-86v4-5p7w referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.vikunja.io/api | >=2.6.0, <2.7.0 all versions |
2.7.0 |
Affected products
- go-vikunja vikunja
Classification
References
-
github.com
/go-vikunja/vikunja/commit/890ca5979d0c770bb5d158362797879c115961af
web
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-pjr3-86v4-5p7w
vendor-advisory, exploit, web, advisory
-
vulncheck.com
/advisories/vikunja-2.6.0-broken-access-control-via-inherited-project-permissions
third-party-advisory
-
github.com
/go-vikunja/vikunja
package
-
vikunja.io
/changelog/vikunja-2.7.0-was-released
web
Sources
- CVE List CVE-2026-111920
- GitHub Advisory GHSA-pjr3-86v4-5p7w
- NVD CVE-2026-111920
- OSV GO-2026-6745
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.