Live › vulnerability › CVE-2026-91985
Go to dashboardIn Vikunja <= 2.5.0, any user with read-only access to a project can call GET /api/v1|v2/projects/{project}/shares/{share} and receive the link share's secret hash. They can exchange it at the unauthenticated POST /api/v1/shares/{hash}/auth for a link-share JWT at the share's permission (read-write or admin) and write to the project. Needs existing project membership and a link share on the project. Password-protected shares still need the password. Fixed in 2.6.0.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| code.vikunja.io/api | go | all versions | – |
| code.vikunja.io/api | go | <= 2.5.0 (before 2.6.0) | 2.6.0 |
2.5.0 is affected2.6.0 or later (go module code.vikunja.io/api v2.6.0)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Vikunja: Read-only project members can obtain any link share's access hash via the single-share read endpoint (v1 and v2) and escalate to the share's permission level in code.vikunja.io/api.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: code.vikunja.io/api before v2.6.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-91985")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.