CVE-2026-91981: Vikunja Link-share Token Can Enumerate Users Vulnerability
MODERATECVE-2026-91981 is a MODERATE link-share token can enumerate users vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Vikunja libraries in the Go ecosystem. The issue involves link-share token can enumerate users through the v2 api. Remediation is available by upgrading affected packages to version 2.6.0.
CVE-2026-91981 at a Glance
How to Fix CVE-2026-91981
To remediate this vulnerability, upgrade all affected Vikunja dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade code.vikunja.io/api to 2.6.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for code.vikunja.io/api
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-91981, inspect your project dependencies for Vikunja:
inspect dependencies for code.vikunja.io/api
Analyze the terminal output to locate any version of Vikunja in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.6.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Vikunja, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-91981 Affected Vikunja Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
code.vikunja.io/api
|
Go |
< 2.6.0
|
2.6.0
|
References
Frequently Asked Questions
What is CVE-2026-91981?
Which Vikunja versions are affected?
What version fixes CVE-2026-91981?
Is code.vikunja.io/api affected?
What CWE is associated with CVE-2026-91981?
How can I check Go dependencies for CVE-2026-91981?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vfxw-3x8p-2vjr",
"modified" : "2026-10-09T20:52:39Z",
"published" : "2026-10-09T20:52:39Z",
"aliases" : [ "CVE-2026-91981" ],
"summary" : "Vikunja: Link-share token can enumerate users through the v2 API",
"details" : "### Summary\nA link-share token, the credential you hand out to let someone view a shared project, can call the v2 user-search endpoints, which it was never meant to reach. The v1 versions of the same endpoints correctly reject link-share tokens; the v2 versions don't. As a result, anyone with a share link can list every member of the shared project (and its parent projects), and can test whether any username exists anywhere on the instance.\n\n### Details\nTwo endpoints are affected:\n\n`GET /api/v2/projects/{id}/users/search` only checks project.CanRead, which a link share satisfies on its own project. With no parameter it returns the full user list, walking up the parent-project chain.\n`GET /api/v2/users?q=<name>` is a global search. It needs a query term, but any term works as an existence oracle: a hit confirms the username exists somewhere on the instance and returns the display name.\n\nEmails are correctly stripped from these responses, so the exposure is limited to identities (usernames and display names), but that's still an instance-wide directory that a share-link holder should never see.\n\nThe fix is to resolve the caller with GetFromAuth in both handlers, so link-share tokens are rejected the same way v1 already rejects them.\n\n### PoC\n1. Get a link-share token. With any account that owns a project, create a read-only link share and note the hash, then exchange it:\n```\nPOST /api/v1/shares/<hash>/auth\n{\"password\":\"\"}\n```\nThe response contains a token, a link-share JWT.\n\n2. Confirm v1 blocks it (the fixed behavior). With that token:\n```\nGET /api/v1/projects/<id>/projectusers\nAuthorization: Bearer <link_share_token>\n```\n→ rejected: the token isn't a user token.\n\n3. Now the vulnerable v2 endpoints, same token:\n```\nGET /api/v2/projects/<id>/users/search\nAuthorization: Bearer <link_share_token>\n```\n→ 200, full list of everyone with access to the project and its parents (id, username, name).\n```\nGET /api/v2/users?q=admin\nAuthorization: Bearer <link_share_token>\n```\n→ 200, a non-empty result confirms the username exists on the instance. Iterate q over a wordlist to enumerate accounts.\n\n### Impact\nInformation disclosure. A link share is a low-trust credential meant to expose one project's contents; here it also exposes the membership of that project's parents and lets the holder probe for any username across the whole instance. Since share links are often forwarded or semi-public, this hands an untrusted recipient a map of internal users and a username-validation oracle useful for phishing and credential stuffing. No account is required beyond possessing a share link. Emails are not exposed.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "code.vikunja.io/api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.6.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.5.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-vfxw-3x8p-2vjr"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-91981"
}, {
"type" : "WEB",
"url" : "https://github.com/go-vikunja/vikunja/pull/3688"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/go-vikunja/vikunja"
}, {
"type" : "WEB",
"url" : "https://github.com/go-vikunja/vikunja/releases/tag/v2.6.0"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/vikunja-before-2.6.0-user-enumeration-via-v2-api"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-863" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-09T20:52:39Z",
"nvd_published_at" : null
}
}