Is CVE-2026-111920 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111920 being exploited in the wild.

How severe is CVE-2026-111920?

Medium severity, with a CVSS score of 4.3, published 17 October 2026.

Which products and versions are affected?

code.vikunja.io/api (Go) SEMVER:introduced=0; Vikunja 2.6.0.

Is there a fix for CVE-2026-111920?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-111920 attacked?

It is attacked over the network.

Am I affected by CVE-2026-111920?

Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111920: Vikunja broken access control in project permissions

CVE-2026-111920 · Severity: medium · CVSS 4.3 · Published 2026-10-17

Vikunja is an open-source project and task management application. In version 2.6.0, a flaw allows a user with high-level permissions on a parent project to automatically inherit those same permissions on child projects, even when the project owner explicitly restricted the user to lower permissions on the child. An attacker could exploit this to modify, delete, or re-share sensitive child projects they should not have access to.

Technologies: code.vikunja.io/api (Go), Vikunja. Vendors: Go, Vikunja.

Quick answers

Is CVE-2026-111920 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111920 being exploited in the wild.
How severe is CVE-2026-111920?: Medium severity, with a CVSS score of 4.3, published 17 October 2026.
Which products and versions are affected?: code.vikunja.io/api (Go) SEMVER:introduced=0; Vikunja 2.6.0.
Is there a fix for CVE-2026-111920?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-111920 attacked?: It is attacked over the network.
Am I affected by CVE-2026-111920?: Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a broken access control (CWE-269) in the getProjectAccessForUser function (pkg/models/project_access.go). The permission resolution engine uses MAX(permission) across the entire reachable project subtree, causing inherited higher permissions to override explicit lower-permission grants on child projects. This is a regression from v2.5.0, which used nearest-ancestor-grant-wins semantics. An authenticated user with a direct ADMIN grant on a parent project and an explicit READ-only grant on a child project will receive ADMIN access to the child, defeating the intended down-restriction.

Affected products

Vikunja Vikunja 2.6.0

Identifiers

CVE-2026-111920
GHSA-pjr3-86v4-5p7w
GO-2026-6745

Timeline

2026-10-03: disclosed
2026-10-17: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.